Fix issue #6, this error occurs only when authenticating with user/password and when the Rundeck host is wrong (IP adresses or "localhost" if hostname is defined).
The fix consits of restarting the authentication sequence if the real Rundeck hostname is different when receiving a HTTP redirect 302 in response of an authentication POST. Because the JSESSIONID cookie is lost if the hostname change during the authentication redirect sequence (debugged with Wireshark).
This fix has been tested successfully with Rundeck Monitor using login/password authentication and IP address instead of Rundeck server host.
Fix issue #6, this error occurs only when authenticating with user/password and when the Rundeck host is wrong (IP adresses or "localhost" if hostname is defined).
The fix consits of restarting the authentication sequence if the real Rundeck hostname is different when receiving a HTTP redirect 302 in response of an authentication POST. Because the JSESSIONID cookie is lost if the hostname change during the authentication redirect sequence (debugged with Wireshark).
This fix has been tested successfully with Rundeck Monitor using login/password authentication and IP address instead of Rundeck server host.