Turn off parser processing for ARG fields?

[eloyd]

The search software won't let me search for "#" because it's too short, so I apologize if this has been dealt with already. Here goes:

We're using ARG1 in a check_nt type service check as the password on the remote system. For sake of example, let's say the password is Nagios#123. Turns out that when we put "Nagios#123" into the arg2 field and save it, what gets created in the Core config files is "Nagios%23123" as if it's being HTML Encoded. Not cool.

How do we turn this off, since we must use the randomly assigned passwords that the customer's security folks provide us, and saying "just give us numbers and letters" won't work.

[tmcdonald]

I've proposed patching the version of Core that is distributed with XI to do two things:

• Remove comment ability entirely (not really needed in most cases)
• Swap out ! for a non-printing character as arg separators

This would let !#; we used basically anywhere in the CCM.

Can I get a amen +1?

[eloyd]

+1
Like
Friend
Retweet
Follow
Praise
#yes
Whatever it takes to make it go.

[tmcdonald]

I'll definitely bring it up to the devs again, but as far as a fix right now I'm thinking it will need to be a resource.cfg entry to "escape" the special characters, unfortunately.

[eloyd]

i just took a moment to look through the XI 5.2.8 release notes and saw this:

Code: Select all

- Fixed using ; and # in $ARGx$ values in the CCM [TPS#8292] -JO

I'd suggest that this is very related to the problem I'm referring to, and is in fact, not working as intended.

[tmcdonald]

Learned something new today. # is only a comment at the beginning of a line in Core, while ; is a comment anywhere. Oh how I miss being in the trenches of Core :)

Jake is fixing this to not escape # but ; still will be for the time-being. Will be fixed in 5.2.9.

[eloyd]

Groovy!