-
Type:
Suggestion
-
Resolution: Duplicate
-
Component/s: User Management
-
None
-
Environment:Crowd used as single source of Users and Groups for
* JIRA
* Confluence
* Bitbucket Server
* Fisheye
*Crowd SSO* is used for all applications.
Several User Directories are configured to grab users from different AD sub-trees.
All Crowd Applications ({{confluence-crowd}} for Confluence, {{stash-crowd}} for Bitbucket Server, and so on...) are configured to use the same User Directories.Crowd used as single source of Users and Groups for * JIRA * Confluence * Bitbucket Server * Fisheye *Crowd SSO* is used for all applications. Several User Directories are configured to grab users from different AD sub-trees. All Crowd Applications ({{confluence-crowd}} for Confluence, {{stash-crowd}} for Bitbucket Server, and so on...) are configured to use the same User Directories.
We have 10.000+ user licences on all application except Stash (5.000 users).
Whenever user logs in to whatever application, she is automatically added to groups
- jira-user
- confluence-users
- stash-users
- fisheye-users
However user is added on User Directory, not application specific! When 5.000 users will login into Confluence, it will render Bitbucket unusable (licence violation, >5.000 users).
If we make a same copy of User Directory specifically for Bitbucket Server:
UD-original auto-adds to:
- jira-user
- confluence-users
- fisheye-users
UD-stash auto-adds to:
- stash-users
then Crowd SSO will stop working.
Please fix this and implement per-application default group membership auto-assignment when user logs for the first time.