-
Suggestion
-
Resolution: Unresolved
-
None
-
12
-
If a user who was not provisioned earlier has a link created with IDP, we should automatically move them to the IDP-linked authentication policy.
- duplicates
-
ACCESS-1041 Automatic assignment of authentication policies
- Under Consideration
[ACCESS-1834] Automatically move users from local policy to IDP linked policy once they are provisioned
Support reference count | Original: 11 | New: 12 |
Support reference count | Original: 10 | New: 11 |
Support reference count | Original: 9 | New: 10 |
Support reference count | Original: 8 | New: 9 |
Support reference count | Original: 7 | New: 8 |
Support reference count | Original: 6 | New: 7 |
Support reference count | Original: 5 | New: 6 |
Support reference count | Original: 4 | New: 5 |
Support reference count | Original: 3 | New: 4 |
somehow not only do we have 2 default policies (we only had one before Atlassian guard activation) but when a user registers using the IDP (the original default policy) they are now all put in the local directory (new additional default policy we didn't set) I mean atleast if they went into the default policy we defined it would be ok.. but now I have a bunch of users in the wrong policy, and all new users going to the wrong policy.