-
Notifications
You must be signed in to change notification settings - Fork 8.1k
security: domain management #22477
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
Merged
sarahsanders-docker
merged 3 commits into
docker:main
from
sarahsanders-docker:auto-provisioning
May 7, 2025
Merged
security: domain management #22477
Changes from 1 commit
Commits
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
131 changes: 131 additions & 0 deletions
131
content/manuals/security/for-admins/domain-management.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,131 @@ | ||
| --- | ||
| description: Learn how to manage domains and users in the Admin Console | ||
| keywords: domain management, security, identify users, manage users | ||
| title: Domain management | ||
| weight: 55 | ||
| --- | ||
|
|
||
| {{< summary-bar feature_name="Domain management" >}} | ||
|
|
||
| Domain management lets you add and verify domains, and enable | ||
| auto-provisioning for users. Auto-provisioning adds users to your | ||
| organization when they sign in with an email address that matches a verified | ||
| domain. | ||
|
|
||
| This simplifies user management, ensures consistent security settings, and | ||
| reduces the risk of unmanaged users accessing Docker without visibility | ||
| or control. | ||
|
|
||
| ## Add a domain | ||
|
|
||
| 1. Sign in to the [Admin Console](https://admin.docker.com/). | ||
| 2. Select your organization or company from the **Choose profile** page. | ||
| If your organization is part of a company, select the company | ||
| and configure the domain for the organization at the company level. | ||
| 3. Under **Security and access**, select **Domain management**. | ||
| 4. Select **Add a domain**. | ||
| 5. Enter your domain and select **Add domain**. | ||
| 6. In the pop-up modal, copy the **TXT Record Value** to verify your domain. | ||
|
|
||
| ## Verify a domain | ||
|
|
||
| Verifying your domain confirms that you own it. To verify, add a TXT record to | ||
| your Domain Name System (DNS) host using the value provided by Docker. This | ||
| value proves ownership and instructs your DNS to publish the record. | ||
|
|
||
| It can take up to 72 hours for the DNS change to propagate. Docker automatically | ||
| checks for the record and confirms ownership once the change is recognized. | ||
|
|
||
| Follow your DNS provider’s documentation to add the **TXT Record Value**. If | ||
| your provider isn't listed, use the steps for other providers. | ||
|
|
||
| > [!TIP] | ||
| > | ||
| > The record name field determines where the TXT record is added in your domain | ||
| (root or subdomain). In general, refer to the following tips for | ||
| adding a record name: | ||
| > | ||
| > - Use `@` or leave the record name empty for root domains like `example.com`, | ||
| depending on your provider. | ||
| > - Don't enter values like `docker`, `docker-verification`, `www`, or your | ||
| domain name. These values may direct to the wrong place. | ||
| > | ||
| > Check your DNS provider's documentation to verify record name requirements. | ||
|
|
||
| {{< tabs >}} | ||
| {{< tab name="AWS Route 53" >}} | ||
|
|
||
| 1. To add your TXT record to AWS, see [Creating records by using the Amazon Route 53 console](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-creating.html). | ||
| 2. TXT record verification can take 72 hours. Once you have waited for | ||
| TXT record verification, return to the **Domain management** page of the | ||
| [Admin Console](https://app.docker.com/admin) and select **Verify** next to | ||
| your domain name. | ||
|
|
||
| {{< /tab >}} | ||
| {{< tab name="Google Cloud DNS" >}} | ||
|
|
||
| 1. To add your TXT record to Google Cloud DNS, see [Verifying your domain with a TXT record](https://cloud.google.com/identity/docs/verify-domain-txt). | ||
| 2. TXT record verification can take 72 hours. Once you have waited for TXT | ||
| record verification, return to the **Domain management** page of the | ||
| [Admin Console](https://app.docker.com/admin) and select **Verify** next to | ||
| your domain name. | ||
|
|
||
| {{< /tab >}} | ||
| {{< tab name="GoDaddy" >}} | ||
|
|
||
| 1. To add your TXT record to GoDaddy, see [Add a TXT record](https://www.godaddy.com/help/add-a-txt-record-19232). | ||
| 2. TXT record verification can take 72 hours. Once you have waited for TXT | ||
| record verification, return to the **Domain management** page of the | ||
| [Admin Console](https://app.docker.com/admin) and select **Verify** next to your | ||
| domain name. | ||
|
|
||
| {{< /tab >}} | ||
| {{< tab name="Other providers" >}} | ||
|
|
||
| 1. Sign in to your domain host. | ||
| 2. Add a TXT record to your DNS settings and save the record. | ||
| 3. TXT record verification can take 72 hours. Once you have waited for TXT | ||
| record verification, return to the **Domain management** page of the | ||
| [Admin Console](https://app.docker.com/admin) and select **Verify** next to | ||
| your domain name. | ||
|
|
||
| {{< /tab >}} | ||
| {{< /tabs >}} | ||
|
|
||
| ## Auto-provisioning | ||
|
|
||
| You must add and verifiy a domain before enabling auto-provisioning. This | ||
|
Check failure on line 97 in content/manuals/security/for-admins/domain-management.md
|
||
| confirms your organization owns the domain. Once a domain is verified, | ||
| Docker can automatically associate matching users with your organization. | ||
| Auto-provisioning does not require an SSO connection. | ||
|
|
||
| > [!IMPORTANT] | ||
| > | ||
| > For domains that are part of an SSO connection, Just-in-Time (JIT) overrides | ||
| auto-provisioning to add users to an organization. | ||
|
|
||
| ### Enable auto-provisioning | ||
|
|
||
| Auto-provisioning is enabled per user. To enable | ||
| auto-provisioning: | ||
|
|
||
| 1. Open the [Admin Console](https://app.docker.com/admin). | ||
| 2. Select **Domain management** from the left-hand navigation. | ||
| 3. Select the **Actions menu** next to the user you want to enable | ||
| auto-provisioning for. | ||
| 4. Select **Enable auto-provisioning**. | ||
| 5. Optional. If enabling auto-provisioning at the company level, select an | ||
| organization for the user. | ||
| 6. Select **Enable** to confirm. | ||
|
|
||
| The **Auto-provisioning** column will update to **Enabled**. | ||
|
|
||
| ### Disable auto-provisioning | ||
|
|
||
| To disable auto-provisioning for a user: | ||
|
|
||
| 1. Open the [Admin Console](https://app.docker.com/admin). | ||
| 2. Select **Domain management** from the left-hand navigation. | ||
| 3. Select the **Actions menu** next to your user. | ||
| 4. Select **Disable auto-provisioning**. | ||
| 5. Select **Disable**. | ||
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -10,6 +10,7 @@ | |
| "-mt-0.5", | ||
| "-mt-4", | ||
| "-mt-8", | ||
| "-top-16", | ||
| "-v", | ||
| "-z-10", | ||
| ".NET", | ||
|
|
||
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.
Uh oh!
There was an error while loading. Please reload this page.