-
Suggestion
-
Resolution: Unresolved
-
Low
-
None
-
None
-
None
-
None
For a customer using AD with JIT provisioning, the "Default Groups" settings under "Application Access" page is currently ignored.
Expected behavior is when JIT users, are created in internal directory, like manually created users, respect this setting to apply default groups to the user's membership when inserted to internal directory.
App Access page says:
When you create a user for a Jira application, that user is automatically added to the application's default group.
But users created via JIT do not respect this setting.
- duplicates
-
SAMLDC-69 Support the ability to add newly created users to groups using just-in-time provisioning
-
- Gathering Interest
-
- is related to
-
CONFSERVER-60578 Make JIT Group Attribute Sync optional and add Default Group Membership
- Gathering Interest
-
JRASERVER-72066 Make JIT Group Attribute Sync optional and add Default Group Membership
- Gathering Interest
- relates to
-
JRASERVER-72388 Local group membership is removed when JIT is enabled.
-
- Closed
-
- mentioned in
-
Page Loading...
[SAMLDC-73] Jira Application Access respect "default group" when using JIT provisioning
Workflow | Original: SAMLDC Workflow v2 [ 4056682 ] | New: JAC Suggestion Workflow 3 [ 4271315 ] |
Status | Original: Verified [ 10005 ] | New: Reviewing [ 11773 ] |
Link |
New:
This issue relates to |
Link | New: This issue is related to CONFSERVER-60578 [ CONFSERVER-60578 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 535107 ] |
Link | New: This issue is related to JRASERVER-72066 [ JRASERVER-72066 ] |
Link | Original: This issue is related to JRASERVER-72066 [ JRASERVER-72066 ] |
Link | New: This issue is related to JRASERVER-72066 [ JRASERVER-72066 ] |
Description |
Original:
For a customer using AD with JIT provisioning, the "Default Groups" settings under "Application Access" page is currently ignored.
Expected behavior is when JIT users, are created in internal directory, like manually created users, respect this setting to apply default groups on first login. |
New:
For a customer using AD with JIT provisioning, the "Default Groups" settings under "Application Access" page is currently ignored.
*Expected behavior* is when JIT users, are created in internal directory, like manually created users, respect this setting to apply default groups to the user's membership when inserted to internal directory. App Access page says: {quote}When you create a user for a Jira application, that user is automatically added to the application's default group. {quote} But users created via JIT do not respect this setting. |
Description |
Original:
For a customer using Azure AD with JIT provisioning, with a large AD footprint, passing all group memberships via SAML is problematic, hitting the 150 group limit.
Customer requests: adding an option to consume a SAML Token, which will work around the user login issue when hitting the 150 group limitation. Once user has required groups when the login JIT automatically maps the user group with Application Access group and add user to it automatically. Also consider the possibility of local AD user directory (not Azure AD) to handle the possible scenario in which the user logs on with JIT but Application Access default groups are not yet setup. |
New:
For a customer using AD with JIT provisioning, the "Default Groups" settings under "Application Access" page is currently ignored.
Expected behavior is when JIT users, are created in internal directory, like manually created users, respect this setting to apply default groups on first login. |