-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 6.3.4, 6.10.0, 6.14.2, 6.14.3
-
Component/s: User - Management
-
None
-
14
-
Severity 3 - Minor
-
3
Summary
When Confluence is connected to Delegated LDAP, users that are already deleted from LDAP side will not be able to be disabled from Confluence
Environment
- Delegated (Internal with LDAP Authentication) LDAP
Steps to Reproduce
- Connect Confluence to an LDAP with Delagated permission
- Login to Confluence as one of the user from the Delegated LDAP
- Create some content in Confluence
- Logout
- Remove this user from LDAP side
- Disable the user in Confluence
Expected Results
- User able to be disabled in Confluence
Actual Results
User unable to be disabled from Confluence. The following error message appears:
User "UserA" could not be disabled. The directory may be read-only.
Even if we recreate the user from LDAP, we'll still unable to disable the user in Confluence side.
Workaround
Disable the user manually by running the following database SQL query:
UPDATE cwd_user SET active = 'F' where user_name = '<the username that we'd like to disable>';
Please always backup your database before performing any alteration in the database side.
- was cloned as
-
JRASERVER-72307 Unable to disable users from Delegated LDAP when the users are removed from LDAP side
-
- Gathering Impact
-
- mentioned in
-
Page Loading...