-
Suggestion
-
Resolution: Fixed
-
None
-
54
-
Confluence 2.7.x now uses the Atlassian User as the underlying user management framework. However, there are situation where:
- There are already local users exist in the Confluence instance
- The local users are a member of some existing local groups with certain permission set
- Having the local username possess the same username in the LDAP server
- Integrating with LDAP leads to:
- The LDAP user (who has the same username as the existing local users) not being a membership of the local groups anymore
- The LDAP user do not possess the group permission/privilege set
It would be nice if Confluence provide the ability to retain the local group membership and permission for LDAP users who have the same username with the local user.
- incorporates
-
CONFSERVER-6885 When LDAP user with the same username as a local user logs in they no longer belong to confluence-users
- Closed
- is related to
-
CONFSERVER-8098 User browser shows duplicate accounts when a user exists both locally and in LDAP
- Closed
-
CONFSERVER-11115 Atlassian-user should support password authentication only to LDAP (like OSUser)
- Closed
-
JRASERVER-24213 Not able to migrate user from 1 directory to another directory
- Closed
- relates to
-
CONFSERVER-17212 OsUser to Atlassian User migration fails when the LDAP users have a different case to the users in the OSUSER table.
- Closed
-
CONFSERVER-7906 Only the LDAP repository a user was found in contributes to their groups
- Closed