Skip to content

security: improve SCIM intro #22647

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 16, 2025
Merged

security: improve SCIM intro #22647

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5e87a41
improve SCIM
sarahsanders-docker May 15, 2025
112aac7
fix lint error
sarahsanders-docker May 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
fix lint error
  • Loading branch information
@sarahsanders-docker
sarahsanders-docker committed May 15, 2025
commit 112aac75d2fb3a4c8db7c48018d4ae7804c67a69
2 changes: 1 addition & 1 deletion content/manuals/security/faqs/general.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,7 @@ Docker Desktop utilizes the host operating system's secure key management for ha

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).

### How do we de-provision users who are not part of our IdP? We use SSO but not SCIM.
### How do we de-provision users who are not part of our IdP? We use SSO but not SCIM

If SCIM isn't enabled, you have to manually remove users from the organization.
SCIM can automate this if your users are added after SCIM is enabled. Any users
Expand Down