-
Suggestion
-
Resolution: Fixed
When using Crowd to provide user management for multiple Atlassian products we would like to ability configure the application configuration in crowd to automatically add an authenticated user, instead of the connected user directory.
For Example, if we have Stash, Jira, and Confluence. Each out of the box works the best if you allow a user to be automatically added upon authentication to the either the jira-users, confluence-users, or the stash-users local group. The user might not need nor have access to all 3, so we need the automatically add functionality at the application level.
The workaround as i see it, is to have a duplicate of the user directory in Crowd, where each application config in crowd is connected to a seperate user directory. This seems wasteful of resources when the user pool amongs all the Atlassian application connected are from the same corporate LDAP/AD user directory. IE there is overlap of users, but all the users could have access to all the applications from the groups their are members.
- is duplicated by
-
- Closed
-
- Closed
- mentioned in
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page")
Page
Failed to load
-
Page
Failed to load
-
Page
Failed to load
-
Page Loading...
-
-
- was cloned as
-
[CWD-3726] All auto group add per application vs user directory
| Workflow | Original: JAC Suggestion Workflow [ 3388323 ] | New: JAC Suggestion Workflow 3 [ 3630306 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Simplified Crowd Development Workflow v2 [ 1393673 ] | New: JAC Suggestion Workflow [ 3388323 ] |
| Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
| Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
| Epic Link | Original: CWD-4705 [ 600142 ] |
| Description |
Original:
{panel:title=Atlassian Update - STARTED - 12 October 2017 |borderStyle=solid|borderColor=#3c78b5|titleBGColor=#3c78b5|bgColor=#e7f4fa}
Hello everyone, Thanks for your votes and comments on this request. Your feedback is highly valuable for us! It helps us to build a better product. I’m happy to say that we’ve started work on this feature to let you auto assign users to groups upon successful log in to specific application. We believe that it will allow you to optimize the usage of your licenses. If you would like to participate in early validation of our solution then please don't hesitate to get in touch with me directly. It will help us to build the right thing that satisfies your needs. We are currently at the early phase of building it and we are hoping to roll it out in the next release of Crowd. We’ll keep you posted! Best regards, Marek Radochonski Senior Product Manager, Crowd [mradochonski@atlassian.com|mailto:mradochonski@atlassian.com] {panel} When using Crowd to provide user management for multiple Atlassian products we would like to ability configure the application configuration in crowd to automatically add an authenticated user, instead of the connected user directory. For Example, if we have Stash, Jira, and Confluence. Each out of the box works the best if you allow a user to be automatically added upon authentication to the either the jira-users, confluence-users, or the stash-users local group. The user might not need nor have access to all 3, so we need the automatically add functionality at the application level. The workaround as i see it, is to have a duplicate of the user directory in Crowd, where each application config in crowd is connected to a seperate user directory. This seems wasteful of resources when the user pool amongs all the Atlassian application connected are from the same corporate LDAP/AD user directory. IE there is overlap of users, but all the users could have access to all the applications from the groups their are members. |
New:
When using Crowd to provide user management for multiple Atlassian products we would like to ability configure the application configuration in crowd to automatically add an authenticated user, instead of the connected user directory.
For Example, if we have Stash, Jira, and Confluence. Each out of the box works the best if you allow a user to be automatically added upon authentication to the either the jira-users, confluence-users, or the stash-users local group. The user might not need nor have access to all 3, so we need the automatically add functionality at the application level. The workaround as i see it, is to have a duplicate of the user directory in Crowd, where each application config in crowd is connected to a seperate user directory. This seems wasteful of resources when the user pool amongs all the Atlassian application connected are from the same corporate LDAP/AD user directory. IE there is overlap of users, but all the users could have access to all the applications from the groups their are members. |
| Remote Link | New: This issue links to "Page (Extranet)" [ 336092 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Verified [ 10005 ] | New: Closed [ 6 ] |
| Fix Version/s | New: 3.1.1 [ 74332 ] |
| Assignee | New: Marek Radochonski [ mradochonski@atlassian.com ] |
| Remote Link | New: This issue links to "Page (Extranet)" [ 325751 ] |
This feature will be available in the upcoming Crowd 3.1.1 release.