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
Domain management lets you add and verify domains, and enable
13
-
auto-provisioning for users. Auto-provisioning adds users to your
14
-
organization when they sign in with an email address that matches a verified
15
-
domain.
12
+
Domain management lets you add and verify domains for your organization, then enable auto-provisioning to automatically add users when they sign in with email addresses that match your verified domains.
16
13
17
-
This simplifies user management, ensures consistent security settings, and
18
-
reduces the risk of unmanaged users accessing Docker without visibility
19
-
or control.
14
+
This approach simplifies user management, ensures consistent security settings, and reduces the risk of unmanaged users accessing Docker without visibility or control.
20
15
21
-
## Add a domain
16
+
## Add and verify a domain
17
+
18
+
Adding a domain requires verification to confirm ownership. The verification process uses DNS records to prove you control the domain.
19
+
20
+
### Add a domain
22
21
23
22
1. Sign in to [Docker Home](https://app.docker.com) and select
24
23
your organization. If your organization is part of a company, select the company
@@ -28,18 +27,13 @@ and configure the domain for the organization at the company level.
28
27
1. Enter your domain and select **Add domain**.
29
28
1. In the pop-up modal, copy the **TXT Record Value** to verify your domain.
30
29
31
-
## Verify a domain
30
+
###Verify a domain
32
31
33
-
Verifying your domain confirms that you own it. To verify, add a TXT record to
34
-
your Domain Name System (DNS) host using the value provided by Docker. This
35
-
value proves ownership and instructs your DNS to publish the record.
32
+
Verification confirms that you own the domain by adding a TXT record to your Domain Name System (DNS) host.
36
33
37
34
It can take up to 72 hours for the DNS change to propagate. Docker automatically
38
35
checks for the record and confirms ownership once the change is recognized.
39
36
40
-
Follow your DNS provider’s documentation to add the **TXT Record Value**. If
41
-
your provider isn't listed, use the steps for other providers.
42
-
43
37
> [!TIP]
44
38
>
45
39
> The record name field determines where the TXT record is added in your domain
@@ -53,81 +47,113 @@ domain name. These values may direct to the wrong place.
53
47
>
54
48
> Check your DNS provider's documentation to verify record name requirements.
55
49
50
+
Follow the steps for your DNS provider to add the **TXT Record Value**. If
51
+
your provider isn't listed, use the steps for "Other providers":
52
+
56
53
{{< tabs >}}
57
54
{{< tab name="AWS Route 53" >}}
58
55
59
-
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).
60
-
1.TXT record verification can take 72 hours. Once you have waited for
61
-
TXT record verification, return to the **Domain management** page of the
56
+
1.Add your TXT record to AWS by following[Creating records by using the Amazon Route 53 console](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-creating.html).
57
+
1.Wait up to 72 hours for TXT record verification.
58
+
1. Return to the **Domain management** page of the
62
59
[Admin Console](https://app.docker.com/admin) and select **Verify** next to
63
60
your domain name.
64
61
65
62
{{< /tab >}}
66
63
{{< tab name="Google Cloud DNS" >}}
67
64
68
-
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).
69
-
1.TXT record verification can take 72 hours. Once you have waited for TXT
70
-
record verification, return to the **Domain management** page of the
65
+
1.Add your TXT record to Google Cloud DNS by following[Verifying your domain with a TXT record](https://cloud.google.com/identity/docs/verify-domain-txt).
66
+
1.Wait up to 72 hoursfor TXT record verification.
67
+
1. Return to the **Domain management** page of the
71
68
[Admin Console](https://app.docker.com/admin) and select **Verify** next to
72
69
your domain name.
73
70
74
71
{{< /tab >}}
75
72
{{< tab name="GoDaddy" >}}
76
73
77
-
1.To add your TXT record to GoDaddy, see[Add a TXT record](https://www.godaddy.com/help/add-a-txt-record-19232).
78
-
1.TXT record verification can take 72 hours. Once you have waited for TXT
79
-
record verification, return to the **Domain management** page of the
80
-
[Admin Console](https://app.docker.com/admin) and select **Verify** next to your
81
-
domain name.
74
+
1.Add your TXT record to GoDaddy by following[Add a TXT record](https://www.godaddy.com/help/add-a-txt-record-19232).
75
+
1.Wait up to 72 hoursfor TXT record verification.
76
+
1. Return to the **Domain management** page of the
77
+
[Admin Console](https://app.docker.com/admin) and select **Verify** next to
78
+
your domain name.
82
79
83
80
{{< /tab >}}
84
81
{{< tab name="Other providers" >}}
85
82
86
83
1. Sign in to your domain host.
87
-
1. Add a TXT record to your DNS settings and save the record.
88
-
1.TXT record verification can take 72 hours. Once you have waited for TXT
89
-
record verification, return to the **Domain management** page of the
84
+
1. Add a TXT record to your DNS settings using the **TXT Record Value** from Docker.
85
+
1.Wait up to 72 hoursfor TXT record verification.
86
+
1. Return to the **Domain management** page of the
90
87
[Admin Console](https://app.docker.com/admin) and select **Verify** next to
91
88
your domain name.
92
89
93
90
{{< /tab >}}
94
91
{{< /tabs >}}
95
92
96
-
## Delete a domain
93
+
## Configure auto-provisioning
94
+
95
+
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.
96
+
97
+
> [!IMPORTANT]
98
+
>
99
+
> 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.
100
+
101
+
### How auto-provisioning works
102
+
103
+
When auto-provisioning is enabled for a verified domain:
104
+
105
+
- Users who sign in to Docker with matching email addresses are automatically added to your organization.
106
+
- Auto-provisioning only adds existing Docker users to your organization, it doesn't create new accounts.
107
+
- Users experience no changes to their sign-in process.
108
+
- Company and organization owners receive email notifications when new users are added.
109
+
- You may need to [manage seats](/manuals/subscription/manage-seats.md) to accomodate new users.
110
+
111
+
### Enable auto-provisioning
97
112
98
-
Deleting a domain removes the assigned TXT record value. To delete a domain:
113
+
Auto-provisioning is configured per domain. To enable it:
99
114
100
115
1. Sign in to [Docker Home](https://app.docker.com) and select
101
116
your organization. If your organization is part of a company, select the company
102
117
and configure the domain for the organization at the company level.
103
118
1. Select **Admin Console**, then **Domain management**.
104
-
1. For the domain you want to delete, section the **Actions** menu, then
105
-
**Delete domain**.
106
-
1. To confirm, select **Delete domain** in the pop-up modal.
119
+
1. Select the **Actions menu** next to the domain you want to enable
120
+
auto-provisioning for.
121
+
1. Select **Enable auto-provisioning**.
122
+
1. Optional. If enabling auto-provisioning at the company level, select an
123
+
organization.
124
+
1. Select **Enable** to confirm.
107
125
108
-
## Audit domains
126
+
The **Auto-provisioning** column will update to **Enabled** for the domain.
127
+
128
+
### Disable auto-provisioning
129
+
130
+
To disable auto-provisioning for a user:
131
+
132
+
1. Sign in to [Docker Home](https://app.docker.com) and select
133
+
your organization. If your organization is part of a company, select the company
134
+
and configure the domain for the organization at the company level.
135
+
1. Select **Admin Console**, then **Domain management**.
136
+
1. Select the **Actions menu** next to your domain.
137
+
1. Select **Disable auto-provisioning**.
138
+
1. Select **Disable** to confirm.
139
+
140
+
## Audit domains for uncaptured users
109
141
110
142
{{< summary-bar feature_name="Domain audit" >}}
111
143
112
-
The domain audit feature identifies uncapture users in an organization.
113
-
Uncaptured users are Docker users who have authenticated to Docker
114
-
using an email address associated with one of your verified domains,
115
-
but they're not a member of your Docker organization.
144
+
Domain audit identifies uncaptured users. Uncaptured users are Docker users who have authenticated using an email address associated with your verified domains but aren't members of your Docker organization.
116
145
117
-
### Known limitations
146
+
### Limitations
118
147
119
-
Domain audit can't identify the following Docker users:
148
+
Domain audit can't identify:
120
149
121
150
- Users who access Docker Desktop without authenticating
122
151
- Users who authenticate using an account that doesn't have an
123
-
email address associated with one of your verified domains.
152
+
email address associated with one of your verified domains
124
153
125
-
Although domain audit can't identify all Docker users,
126
-
you can enforce sign-in to prevent unidentifiable users from accessing
127
-
Docker Desktop in your environment. For more information,
128
-
see [Enforce sign-in](/manuals/enterprise/security/enforce-sign-in/_index.md).
154
+
To prevent unidentifiable users from accessing Docker Desktop, [enforce sign-in](/manuals/enterprise/security/enforce-sign-in/_index.md).
129
155
130
-
### Audit your domain for uncaptured users
156
+
### Run a domain audit
131
157
132
158
1. Sign in to [Docker Home](https://app.docker.com) and choose your
133
159
company.
@@ -137,68 +163,30 @@ of uncaptured users.
137
163
138
164
The CSV file contains the following columns:
139
165
140
-
- Name: Name of the Docker user
141
-
- Username: Docker ID of the Docker user
142
-
- Email: Email address of the Docker user
166
+
- Name: Docker user's display name
167
+
- Username: Docker ID of the user
168
+
- Email: Email address of the user
143
169
144
170
### Invite uncaptured users
145
171
146
-
You can invite all uncaptured users to your organization using the exported
172
+
You can bulk invite uncaptured users to your organization using the exported
147
173
CSV file. For more information on bulk inviting users, see
0 commit comments