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
Copy file name to clipboardExpand all lines: content/manuals/security/faqs/general.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,7 +68,7 @@ Docker Desktop utilizes the host operating system's secure key management for ha
68
68
69
69
This is applicable only when using Docker Hub's application-level password versus SSO/SAML. For users created through SSO Just-in-Time or SCIM provisioning, Docker Hub doesn't store passwords. For all other users, application-level passwords are salt-hashed in storage (SHA-256) and encrypted in transit (TLS).
70
70
71
-
### How do we de-provision users who are not part of our IdP? We use SSO but not SCIM.
71
+
### How do we de-provision users who are not part of our IdP? We use SSO but not SCIM
72
72
73
73
If SCIM isn't enabled, you have to manually remove users from the organization.
74
74
SCIM can automate this if your users are added after SCIM is enabled. Any users
0 commit comments