Steps to reproduce:

1. Set up iLO monitoring using the HPE iLO over http template
2. Use a password with a " symbol in it
3.  

Result:

591837:20250114:133320.305 [ HPE iLO ] Received response with status code 401: {"error":{"code":"iLO.0.10.ExtendedInfo","message":"See @Message.ExtendedInfo for more information.","@Message.ExtendedInfo":[

{"MessageId":"iLO.2.24.UnauthorizedLoginAttempt"}

]}}
591837:20250114:133320.306 [ HPE iLO ] ERROR: Authentication failed with status code 401: {"error":{"code":"iLO.0.10.ExtendedInfo","message":"See @Message.ExtendedInfo for more information.","@Message.ExtendedInfo":[

{"MessageId":"iLO.2.24.UnauthorizedLoginAttempt"}

]}}.
Expected:

Succesful login and working monitoring

 

I have added some debugging statements to the apiAuth function in the iLO template:

        Zabbix.log(4, '[ HPE iLO ] Debug auth: '+ JSON.stringify(auth_data));
        Zabbix.log(4, '[ HPE iLO ] Debug auth2: '+ ilo.params.password);

The result:

591837:20250114:133620.255 [ HPE iLO ] Debug auth: {"UserName":"zabbix","Password":"Welkom123\\\""}
591837:20250114:133620.255 [ HPE iLO ] Debug auth2: Welkom123\"

 

It looks like the JSON.stringify function is escaping the password!

This used to work before Zabbix 7.2