Actions
Bug #4403
closedAuthentification to Rudder from LDAP should not require to touch WAR file
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
System integration
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Hello,
I'm using LDAP (AD) to auth my rudder users and thus uses the official guide to configure LDAP. This requires to extract the rudder.war file and keep it as a directory in which one would modify a xml file to support LDAP auth.
This wouldn't be an issue if it wouldn't break updates :(
At least with RPM, rudder-webapp package can't upgrade itself successfully if LDAP config has been setup. The culprit is the directory, cpio during the package upgrade, tries to change rudder.war directory by the new rudder.war file and fails.
If the file requiring modification could be put in /opt/rudder/etc - or even better as a configuration option in web interface - this would make upgrade process easier.
Thanks,
Olivier
Actions