Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Not a bug
Priority: High
Fix Version/s: None
Affects Version/s: 3.5
Component/s: None
Labels:

Bug Fix Policy:
View Atlassian Server bug fix policy

Description

When using Confluence with delegated LDAP user management, if the configuration is not set to READ/WRITE,
Confluence refuses to disable or remove a user.

What happens is that Confluence tries to disable the user in LDAP, even in READ ONLY mode and thus an exception is given:

User "xxxxxx" could not be disabled. The directory may be read-only.

Even if the user hasn't contributed with any content, it becomes unable to be disabled unless using READ/WRITE configuration.

Update

This was closed as not a bug, because this behaviour is by design. The option to disable a user in a Read Only directory was removed in 5.1.4. We have opened a feature request to allow disabling of users in a Read Only directory here.

Attachments

Issue Links

has a derivative of

CONFSERVER-29510 Allow disabling users which are sourced from a read-only LDAP directory

Gathering Interest

is duplicated by

CONFSERVER-25542 Cannot disable user of a CONNECTOR LDAP User Directory in Confluence

Closed

is related to

CWD-2478 LDAP Delegate: Synchronize with AD to disable deleted users

Closed

relates to

CONFSERVER-16477 Provide the ability to filter out deactivated users from the people directory

Closed

mentioned in: Page Loading...; Wiki Page Loading...; Wiki Page Loading...; Wiki Page Loading...; Wiki Page Loading...; Wiki Page Loading...; Wiki Page Loading...; Wiki Page Loading...

(7 mentioned in)

Activity

People

Assignee:: fabs

Reporter:: Rodrigo Girardi Adami

Votes:: 23 Vote for this issue

Watchers:: 21 Start watching this issue

Dates

Created:: 15/Apr/2011 3:01 PM

Updated:: 11/Oct/2018 8:51 AM

Resolved:: 13/Aug/2013 10:52 PM