-
Notifications
You must be signed in to change notification settings - Fork 8.2k
SCIM jit edits #24600
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.
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
Open
akristen
wants to merge
5
commits into
docker:main
Choose a base branch
from
akristen:scim-jit-edits
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
SCIM jit edits #24600
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
5a49d2a
initial commit
akristen a8b9c55
update
akristen aceebb0
this was awful; redirect nightmare
akristen 5f762aa
remove random troubleshooting folder and put sso and scim troubleshoo…
akristen c03ffc8
reorganized provisioning; split domain management into two topics sin…
akristen File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
53 changes: 53 additions & 0 deletions
53
content/manuals/enterprise/security/provisioning/auto-provisioning.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,53 @@ | ||
| --- | ||
| title: Auto-provisioning | ||
| linkTitle: Auto-provisioning | ||
| description: Learn how Just-in-Time provisioning works with your SSO connection. | ||
| keywords: user provisioning, just-in-time provisioning, JIT, autoprovision, Docker Admin, admin, security | ||
| weight: 10 | ||
| aliases: | ||
| - /security/for-admins/provisioning/just-in-time/ | ||
| --- | ||
|
|
||
| Auto-provisioning automatically adds users to your organization when they sign in with email addresses that match your verified domains. You must verify a domain before enabling auto-provisioning. | ||
|
|
||
| > [!IMPORTANT] | ||
| > | ||
| > For domains that are part of an SSO connection, Just-in-Time (JIT) provisioning takes precedence over auto-provisioning when adding users to an organization. | ||
|
|
||
| ### Overview | ||
|
|
||
| When auto-provisioning is enabled for a verified domain: | ||
|
|
||
| - Users who sign in to Docker with matching email addresses are automatically added to your organization. | ||
| - Auto-provisioning only adds existing Docker users to your organization, it doesn't create new accounts. | ||
| - Users experience no changes to their sign-in process. | ||
| - Company and organization owners receive email notifications when new users are added. | ||
| - You may need to [manage seats](/manuals/subscription/manage-seats.md) to accommodate new users. | ||
|
|
||
| ### Enable auto-provisioning | ||
|
|
||
| Auto-provisioning is configured per domain. To enable it: | ||
|
|
||
| 1. Sign in to [Docker Home](https://app.docker.com) and select | ||
| your company or organization. | ||
| 1. Select **Admin Console**, then **Domain management**. | ||
| 1. Select the **Actions menu** next to the domain you want to enable | ||
| auto-provisioning for. | ||
| 1. Select **Enable auto-provisioning**. | ||
| 1. Optional. If enabling auto-provisioning at the company level, select an | ||
| organization. | ||
| 1. Select **Enable** to confirm. | ||
|
|
||
| The **Auto-provisioning** column will update to **Enabled** for the domain. | ||
|
|
||
| ### Disable auto-provisioning | ||
|
|
||
| To disable auto-provisioning for a user: | ||
|
|
||
| 1. Sign in to [Docker Home](https://app.docker.com) and select | ||
| your organization. If your organization is part of a company, select the company | ||
| and configure the domain for the organization at the company level. | ||
| 1. Select **Admin Console**, then **Domain management**. | ||
| 1. Select the **Actions menu** next to your domain. | ||
| 1. Select **Disable auto-provisioning**. | ||
| 1. Select **Disable** to confirm. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
59 changes: 59 additions & 0 deletions
59
content/manuals/enterprise/security/provisioning/scim/_index.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,59 @@ | ||
| --- | ||
| title: SCIM overview | ||
| linkTitle: SCIM | ||
| weight: 20 | ||
| description: Learn how System for Cross-domain Identity Management works and how to set it up. | ||
| keywords: SCIM, SSO, user provisioning, de-provisioning, role mapping, assign users | ||
| aliases: | ||
| - /security/for-admins/scim/ | ||
| - /docker-hub/scim/ | ||
| - /security/for-admins/provisioning/scim/ | ||
| --- | ||
|
|
||
| {{< summary-bar feature_name="SSO" >}} | ||
|
|
||
| Automate user management for your Docker organization using System for | ||
| Cross-domain Identity Management (SCIM). SCIM automatically provisions and | ||
| de-provisions users, synchronizes team memberships, and keeps your Docker | ||
| organization in sync with your identity provider. | ||
|
|
||
| This page shows you how to automate user provisioning and de-provisioning for | ||
| Docker using SCIM. | ||
|
|
||
| ## Prerequisites | ||
|
|
||
| Before you begin, you must have: | ||
|
|
||
| - SSO configured for your organization | ||
| - Administrator access to Docker Home and your identity provider | ||
|
|
||
| ## How SCIM works | ||
|
|
||
| SCIM automates user provisioning and de-provisioning for Docker through your | ||
| identity provider. After you enable SCIM, any user assigned to your | ||
| Docker application in your identity provider is automatically provisioned and | ||
| added to your Docker organization. When a user is removed from the Docker | ||
| application in your identity provider, SCIM deactivates and removes them from | ||
| your Docker organization. | ||
|
|
||
| In addition to provisioning and removal, SCIM also syncs profile updates like | ||
| name changes made in your identity provider. You can use SCIM alongside Docker's | ||
| default Just-in-Time (JIT) provisioning or on its own with JIT disabled. | ||
|
|
||
| SCIM automates: | ||
|
|
||
| - Creating users | ||
| - Updating user profiles | ||
| - Removing and deactivating users | ||
| - Re-activating users | ||
| - Group mapping | ||
|
|
||
| > [!NOTE] | ||
| > | ||
| > SCIM only manages users provisioned through your identity provider after | ||
| > SCIM is enabled. It cannot remove users who were manually added to your Docker | ||
| > organization before SCIM was set up. | ||
| > | ||
| > To remove those users, delete them manually from your Docker organization. | ||
| > For more information, see | ||
| > [Manage organization members](/manuals/admin/organization/members.md). | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question: I am not really familiar with SCIM at all, but, does this also apply if you (for whatever reason) manually add a user to an organization (they are not provisioned through SCIM). Or only if they were manually added "before SCIM was set up"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question. Do you mean users who are manually added after some method of provisioning is enabled in an org (auto/jit/scim)? Let me loop into @madisonsilva for a for sure answer -- i don't want to make assumptions, since the differences between the 3 provisioning methods are a bit subtle.