[CWD-4743] Default group memberships for Applications

Type: Suggestion
Resolution: Duplicate
Fix Version/s: 3.1.1
Component/s: User Management
Labels:
None
Environment:

Hide
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.

Show
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.

Feedback Policy:

Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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.

duplicates

CWD-3726 All auto group add per application vs user directory

Closed

CWD-4693 Allow Crowd to add user into a group automatically based on Application when user first authenticate

Closed

KRAK-245 You do not have permission to view this issue

mentioned in: Page Failed to load; Page Failed to load

was cloned as: KRAK-239 Loading...

(1 was cloned as)

Lukasz Pater added a comment - 27/Nov/2017 10:00 AM

This feature will be available in the upcoming Crowd 3.1.1 release.

Lukasz Pater added a comment - 27/Nov/2017 10:00 AM This feature will be available in the upcoming Crowd 3.1.1 release.

Miroslav Kralik added a comment - 13/Mar/2017 10:38 AM

We had to turn off the Crowd SSO for Bitbucket because of this and manage auto groups in different Directory. This way the Crowd SSO loses one of its core benefits.

Miroslav Kralik added a comment - 13/Mar/2017 10:38 AM We had to turn off the Crowd SSO for Bitbucket because of this and manage auto groups in different Directory. This way the Crowd SSO loses one of its core benefits.

Mira Hedl added a comment - 23/Jun/2016 6:35 AM

Bug itself is in the design, not in bad implementation of that design.

Mira Hedl added a comment - 23/Jun/2016 6:35 AM Bug itself is in the design, not in bad implementation of that design.

Assignee:: Unassigned

Reporter:: Mira Hedl

Votes:: 7 Vote for this issue

Watchers:: 9 Start watching this issue

Created:: 23/Jun/2016 6:33 AM

Updated:: 19/Sep/2019 5:51 AM

Resolved:: 24/May/2017 11:42 AM

Details

Description

Attachments

Issue Links

Forms

Activity

Collapse comment: Lukasz Pater added a comment - 27/Nov/2017 10:00 AM

Expand comment: Lukasz Pater added a comment - 27/Nov/2017 10:00 AM

Collapse comment: Miroslav Kralik added a comment - 13/Mar/2017 10:38 AM

Expand comment: Miroslav Kralik added a comment - 13/Mar/2017 10:38 AM

Collapse comment: Mira Hedl added a comment - 23/Jun/2016 6:35 AM

Expand comment: Mira Hedl added a comment - 23/Jun/2016 6:35 AM

People

Dates