-
Suggestion
-
Resolution: Obsolete
-
None
-
None
-
None
In JIRA Service Desk, it would be useful if on authentication from the customer portal there could be a way to ignore the auto adding of default groups (delegated LDAP with copy on login for example).
Perhaps an extra parameter can be included in the login request, that if present will tell Crowd to not auto add any groups.
However, if the same LDAP user was then to login through JIRA itself, they should still be updated by being auto-added to the configured default groups
- relates to
-
JSDCLOUD-1248 Creating user on first login through Customer Portal shouldn't count against the JIRA license
- Closed
-
JSDSERVER-1248 Creating user on first login through Customer Portal shouldn't count against the JIRA license
- Closed
[CWD-4180] Can authentication be told to ignore auto adding default groups
Workflow | Original: JAC Suggestion Workflow [ 3388697 ] | New: JAC Suggestion Workflow 3 [ 3630779 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1392148 ] | New: JAC Suggestion Workflow [ 3388697 ] |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Link |
New:
This issue relates to |
Resolution | New: Obsolete [ 11 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Workflow | Original: Crowd Development Workflow v2 [ 786344 ] | New: Simplified Crowd Development Workflow v2 [ 1392148 ] |
Description |
Original:
In JIRA Service Desk, it would be useful if on authentication from the customer portal there could be a way to ignore the auto adding of default groups.
Perhaps an extra parameter can be included in the login request, that if present will tell Crowd to not auto add any groups. |
New:
In JIRA Service Desk, it would be useful if on authentication from the customer portal there could be a way to ignore the auto adding of default groups (delegated LDAP with copy on login for example).
Perhaps an extra parameter can be included in the login request, that if present will tell Crowd to not auto add any groups. However, if the same LDAP user was then to login through JIRA itself, they should still be updated by being auto-added to the configured default groups |
Security | Original: Reporters and Developers [ 10071 ] |
As per the link issue (
JSD-1248) when logging in for the first time through the Customer Portal in Service Desk, the use-case is that they should not be added to the jira-users defualt group (if configured) and consume a JIRA license when they can be treated as a free external customer in the SD context. However if they later log in through JIRA, they would still be added to the default groups and consume a license at that point.