-
Suggestion
-
Resolution: Unresolved
-
277
-
Currently the authentication policies do not support automatic assignment which requires manual action to assign users to policies when they are created.
Suggestion:
- Make SCIM synced groups be able to assign authentication policies.
- Also consider, automatically switching an (existing) account to an SSO policy when they are provisioned and non-billable when they are not.
The use case I can share for this is:
We want only a group of people to be enforced SSO so we make the default authentication policy to be one that is not enforced with SSO but now the need to manually add users to that group of people that should have enforced SSO arises.
- duplicates
-
ACCESS-1037 Allow org admins to be able to add groups to the authentication policies, especially, groups being synced by user provisioning
- Closed
-
ACCESS-1228 Rules for automatic membership to a non-billable authentication policy
- Closed
- is duplicated by
-
ACCESS-1228 Rules for automatic membership to a non-billable authentication policy
- Closed
-
ACCESS-1834 Automatically move users from local policy to IDP linked policy once they are provisioned
- Gathering Interest
-
ACCESS-1905 Provide the ability to retroactively add Managed accounts to Authentication Policy when marked as default
- Gathering Interest
- links to
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- relates to
-
ENT-367 Loading...
[ACCESS-1041] Automatic assignment of authentication policies
Support reference count | Original: 276 | New: 277 |
Remote Link | New: This issue links to "Page (Confluence)" [ 1013586 ] |
Support reference count | Original: 277 | New: 276 |
Support reference count | Original: 276 | New: 277 |
Support reference count | Original: 274 | New: 276 |
Support reference count | Original: 272 | New: 274 |
Assignee | Original: Holly Makris [ d056dd6d7b90 ] | New: Kunwardeep Singh [ 5cd8def7e384 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 1000519 ] |
Support reference count | Original: 271 | New: 272 |
Can we have an update from Atlassian on this one? It has been around for 4 years. Its killing us really. Not all cohorts in our domain use the same tenant. Some use SSO, some dont. Every single new user is a manual process of moving to one auth policy or another. Linking to an automatically maintained group would resolve our issue immediately.