You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our setup we use Tomcat to deploy Rundeck, but since Tomcat uses AJP, there is an issue with the new 4 preauth lines added to the config file: more precisely, the rundeck.security.authorization.preauthenticated.userNameHeader = "" breaks our config; removing or commenting out that line works for us. As preauth, we use Shibboleth based on AD.
The patch we are currently using is shown in the What behaviour did you expect instead section. We'd be glad to provide you with a PR if that solution would be accepted.
Best regards,
Philippe
Affected Puppet, Ruby, OS and module versions/distributions
Hello,
In our setup we use Tomcat to deploy Rundeck, but since Tomcat uses AJP, there is an issue with the new 4 preauth lines added to the config file: more precisely, the
rundeck.security.authorization.preauthenticated.userNameHeader = ""
breaks our config; removing or commenting out that line works for us. As preauth, we use Shibboleth based on AD.The patch we are currently using is shown in the What behaviour did you expect instead section. We'd be glad to provide you with a PR if that solution would be accepted.
Best regards,
Philippe
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
When trying to connect to Rundeck, previously working, we get an error message.
We found out that the problem was related to preauth config, more precisely to the userNameHeader being empty.
What behaviour did you expect instead
To have these lines not added if the values are not defined, e.g.
Output log
Any additional information you'd like to impart
The text was updated successfully, but these errors were encountered: