Project

General

Profile

Actions

Bug #4403

closed

Authentification to Rudder from LDAP should not require to touch WAR file

Added by Olivier Mauras almost 11 years ago. Updated over 10 years ago.

Status:
Released
Priority:
1 (highest)
Category:
System integration
Target version:
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


Subtasks 3 (0 open3 closed)

Bug #4681: Typo: missing "LDAP" in the password commentReleasedNicolas CHARLES2014-03-27Actions
Bug #4678: Migration script for LDAP authenticationReleasedVincent MEMBRÉ2014-03-27Actions
Bug #4679: Correct a typo in the LDAP filter exampleReleasedJonathan CLARKE2014-03-27Actions

Related issues 1 (0 open1 closed)

Related to Rudder - Bug #4680: Update documentation for LDAP authenticationReleasedJonathan CLARKE2014-03-27Actions
Actions

Also available in: Atom PDF