Nagios Support Forum

I am on NagiosXI 2024R1.4.3 and have noted that when I use with the Windows or NCPA wizard, the token is not correctly configured in the actual check for the service.

While the token is not particularly complex, it does contain a ( and an @ symbol.

After running the Wizard, I need to manual amend each service and wrap the token with quotes ''

Is there any solution to this, or do I just need a token with no symbols?

Thanks

NCAP client version is 2.4.1. I am having issues upgrading to a later release - but that is another issue

jdk wrote: ↑Thu Jun 12, 2025 10:29 am NCAP client version is 2.4.1. I am having issuesSprunki 1996 upgrading to a later release - but that is another issue

I thought I was the only one having trouble updating to the new version?

Edit: Sorry, I somehow missed the wizard part of the original post. Doh!

I'd look at the command defined under commands. If the token isn't single quoted, I'd quote it. There's not much difference in single and double quotes other than doubles are interpreted by the shell--meaning $ in a token could be interpreted as a variable, for example.
I did a search and it suggested that the token is user defined. Don't use silly characters in the token. That said, the devs should make allowances for silly things we users can use.
You may want to put the token in resource(s).cfg (I always forget) if it's currently in multiple service definitions.

So, I used a security token without the ) in the token and all has worked. The wizard process should really be amended to ensure the string it creates wraps the token in quotes. Anyway, I just need to get my security team to agree to use a less complex token.