-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
8
-
NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.
It would be good if there is an option for an admin to select which user directory the new user should be added into on adding new user.
Possible scenarios
- Adding a new user to INTERNAL (or any non-first) directory is not possible if DELEGATING directory is the first in user directories list.
- Adding a new user to multiple user directories is not possible. Perhaps an admin wanted to have few users added to DELEGATING and INTERNAL directory. Reason could be that when LDAP is down/inaccessible, these users still can login using their INTERNAL passwords.
Workaround
Confluence Admin can swap the order of User Directories since currently in Confluence, the new user will get created in the first directory with write access rights listed in User Directories.
Further finding
JIRA has done this well, see JRA-23933. In JIRA, a dropdown option now will appear once there is an INTERNAL and at least one DELEGATING directory:
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
- is related to
-
- Closed
-
- Closed
[ID-8985] Provide an option to select user directory on adding/deleting users
Wow. A five year old bug that's solved in another one of your products? That's crazy. I mean.. we can't add users. That's BIG.
Please provide a solution for this. Something like https://jira.atlassian.com/browse/JRA-23933 would be great.
Same issue and this should be considered a show stopper IMO when it comes to security with the product. Not being able to monitor who is gaining access to the dashboard is a problem with the copy user at login. We need to be able to assign directories as admins so we can keep an eye on who is gaining access and at what level.
I just disabled the "Copy User on Login" setting for our two directories because it was resulting in some undesirable changes being re-written from the directories when users logged in. However, this action puts me squarely in the situation that this ticket describes - that Confluence doesn't actually allow me to add users from different directories (2 LDAP directories and the internal directory for my setup).
Note that when using the workaround specified in the description and selecting the option to not send out an email notification, Confluence incorrectly requires a password to be set for the LDAP user.
+1
More than 4 years later (Version 5.8.6) it is still a pain to manage users from different directories in Confluence. (Internal and delegated LDAP)
It's so easy in JIRA with the ability to choose directory when adding a user.
Why are they such technical differences in Atlassian product ?
After Merging your design, could you please merge/adapt the code so that administering JIRA or Confluence behave the same way ?
Robert Stoffers
added a comment - This should be simple. This sums up my feelings on it: http://www.youtube.com/watch?v=QCniMXdbO6c
Robert Stoffers
added a comment - This should be simple. This sums up my feelings on it: http://www.youtube.com/watch?v=QCniMXdbO6c
Adding my voice to this: please make it easy to choose between 'local' and 'directory' authentication for a user, given that if the latter is selected, the username matches a user attribute from the directory. This is present in JIRA, so get someone to port the feature across to remove this inconsistency between products and improve functionality.
-R