You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This page helps troubleshoot common user provisioning issues including user roles, attributes, and unexpected account behavior with SCIM and Just-in-Time (JIT) provisioning.
@@ -21,10 +21,10 @@ IdP. This issue usually surfaces as incorrect role or team assignment.
21
21
### Causes
22
22
23
23
- JIT provisioning is enabled, and Docker is using values from your IdP's
24
-
SSO login flow to provision the user, which overrides
25
-
SCIM-provided attributes.
24
+
SSO login flow to provision the user, which overrides
25
+
SCIM-provided attributes.
26
26
- SCIM was enabled after the user was already provisioned via JIT, so SCIM
27
-
updates don't take effect.
27
+
updates don't take effect.
28
28
29
29
### Affected environments
30
30
@@ -37,7 +37,7 @@ updates don't take effect.
37
37
1. Sign in to Docker as a user via SSO.
38
38
1. Enable SCIM and set role/team attributes for that user.
39
39
1. SCIM attempts to update the user's attributes, but the role or team
40
-
assignment does not reflect changes.
40
+
assignment does not reflect changes.
41
41
42
42
### Solutions
43
43
@@ -58,7 +58,7 @@ and role assignment.
58
58
If you prefer to keep JIT enabled:
59
59
60
60
- Make sure your IdP's SSO attribute mappings match the values being sent
61
-
by SCIM.
61
+
by SCIM.
62
62
- Avoid configuring SCIM to override attributes already set via JIT.
63
63
64
64
This option requires strict coordination between SSO and SCIM attributes
@@ -83,4 +83,4 @@ existing user:
83
83
> [!WARNING]
84
84
>
85
85
> Deleting a user removes their resource ownership (e.g., repositories).
0 commit comments