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 audit identifies uncaptured users in an organization. Uncaptured users are Docker users who have authenticated to Docker using an email address associated with one of your verified domains, but they're not a member of your organization in Docker. You can audit domains on organizations that are part of the Docker Business subscription. To upgrade your existing account to a Docker Business subscription, see [Upgrade your subscription](/subscription/upgrade/).
14
+
Domain management identifies uncaptured users in an organization. Uncaptured users
15
+
are Docker users who have authenticated to Docker using an email address
16
+
associated with one of your verified domains, but they're not a member of your
17
+
organization in Docker. You can audit domains on organizations that are part of
18
+
the Docker Business subscription. To upgrade your existing account to a Docker
19
+
Business subscription, see [Upgrade your subscription](/subscription/upgrade/).
15
20
16
-
Uncaptured users who access Docker Desktop in your environment may pose a security risk because your organization's security settings, like Image Access Management and Registry Access Management, aren't applied to a user's session. In addition, you won't have visibility into the activity of uncaptured users. You can add uncaptured users to your organization to gain visibility into their activity and apply your organization's security settings.
21
+
Uncaptured users who access Docker Desktop in your environment may pose a
22
+
security risk because your organization's security settings, like Image Access
23
+
Management and Registry Access Management, aren't applied to a user's session.
24
+
In addition, you won't have visibility into the activity of uncaptured users.
25
+
You can add uncaptured users to your organization to gain visibility into their
26
+
activity and apply your organization's security settings.
17
27
18
28
Domain audit can't identify the following Docker users in your environment:
19
29
20
30
- Users who access Docker Desktop without authenticating
21
-
- Users who authenticate using an account that doesn't have an email address associated with one of your verified domains
31
+
- Users who authenticate using an account that doesn't have an email address
32
+
associated with one of your verified domains
22
33
23
-
Although domain audit can't identify all Docker users in your environment, you can enforce sign-in to prevent unidentifiable users from accessing Docker Desktop in your environment. For more details about enforcing sign-in, see [Configure registry.json to enforce sign-in](../for-admins/enforce-sign-in/_index.md).
34
+
Although domain audit can't identify all Docker users in your environment, you
35
+
can enforce sign-in to prevent unidentifiable users from accessing Docker
36
+
Desktop in your environment. For more details about enforcing sign-in, see
37
+
[Configure registry.json to enforce sign-in](../for-admins/enforce-sign-in/_index.md).
24
38
25
39
> [!TIP]
26
40
>
27
-
> You can use endpoint management (MDM) software to identify the number of Docker Desktop instances and their versions within your environment. This can provide accurate license reporting, help ensure your machines use the latest version of Docker Desktop, and enable you to [enforce sign-in](enforce-sign-in/_index.md).
41
+
> You can use endpoint management (MDM) software to identify the number of
42
+
Docker Desktop instances and their versions within your environment. This can
43
+
provide accurate license reporting, help ensure your machines use the latest
44
+
version of Docker Desktop, and enable you to [enforce sign-in](enforce-sign-in/_index.md).
@@ -35,7 +52,9 @@ Although domain audit can't identify all Docker users in your environment, you c
35
52
36
53
Before you audit your domains, review the following required prerequisites:
37
54
38
-
- Your organization must be part of a Docker Business subscription. To upgrade your existing account to a Docker Business subscription, see [Upgrade your subscription](../../subscription/change.md).
55
+
- Your organization must be part of a Docker Business subscription. To upgrade
56
+
your existing account to a Docker Business subscription, see
57
+
[Upgrade your subscription](../../subscription/change.md).
39
58
- You must [add and verify your domains](./single-sign-on/configure/_index.md#step-one-add-and-verify-your-domain).
40
59
41
60
> [!IMPORTANT]
@@ -59,3 +78,29 @@ Before you audit your domains, review the following required prerequisites:
59
78
{{< /tab >}}
60
79
{{< /tabs >}}
61
80
81
+
## Auto-provisioning
82
+
83
+
Auto-provisioning adds users automatically to your organization.
84
+
85
+
> [!IMPORTANT]
86
+
>
87
+
> For domains that are part of an SSO connection, Just-in-Time (JIT) overrides auto-provisioning to add users to an organization.
88
+
89
+
### Enable auto-provisioning
90
+
91
+
1. Open the [Admin Console](https://app.docker.com/admin).
92
+
2. Select **Domain management** from the left-hand navigation.
93
+
3. Select the **Actions menu** next to your user.
94
+
4. Select **Enable auto-provisioning**.
95
+
5. Optional. If enabling auto-provisioning at the company level, select an organization for the user.
96
+
6. Select **Enable** to confirm.
97
+
98
+
The **Auto-provisioning** column will update to **Enabled**.
99
+
100
+
### Disable auto-provisioning
101
+
102
+
1. Open the [Admin Console](https://app.docker.com/admin).
103
+
2. Select **Domain management** from the left-hand navigation.
0 commit comments