Skip to content

security: add teams to enforce sign-in #22718

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 1 commit into from
Jun 4, 2025
Merged

security: add teams to enforce sign-in #22718

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
18 changes: 12 additions & 6 deletions content/manuals/security/for-admins/enforce-sign-in/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,18 +16,22 @@ weight: 30
By default, members of your organization can use Docker Desktop without signing
in. When users don’t sign in as a member of your organization, they don’t
receive the [benefits of your organization’s
subscription](../../../subscription/details.md) and they can circumvent [Docker’s
security features](/manuals/security/for-admins/hardened-desktop/_index.md) for your organization.
subscription](../../../subscription/details.md) and they can circumvent
[Docker’s
security features](/manuals/security/for-admins/hardened-desktop/_index.md) for
your organization.

There are multiple methods for enforcing sign-in, depending on your companies' set up and preferences:
There are multiple methods for enforcing sign-in, depending on your companies'
set up and preferences:
- [Registry key method (Windows only)](methods.md#registry-key-method-windows-only){{< badge color=green text="New" >}}
- [Configuration profiles method (Mac only)](methods.md#configuration-profiles-method-mac-only){{< badge color=green text="New" >}}
- [`.plist` method (Mac only)](methods.md#plist-method-mac-only){{< badge color=green text="New" >}}
- [`registry.json` method (All)](methods.md#registryjson-method-all)

## How is sign-in enforced?

When Docker Desktop starts and it detects a registry key, `.plist` file, or `registry.json` file, the following occurs:
When Docker Desktop starts and it detects a registry key, `.plist` file, or
`registry.json` file, the following occurs:

- A **Sign in required!** prompt appears requiring the user to sign
in as a member of your organization to use Docker Desktop. ![Enforce Sign-in
Expand All @@ -42,11 +46,13 @@ When Docker Desktop starts and it detects a registry key, `.plist` file, or `reg

> [!NOTE]
>
> Enforcing sign-in for Docker Desktop does not impact accessing the Docker CLI. CLI access is only impacted for organizations that enforce single sign-on.
> Enforcing sign-in for Docker Desktop does not impact accessing the Docker CLI.
CLI access is only impacted for organizations that enforce single sign-on.

## Enforcing sign-in versus enforcing single sign-on (SSO)

[Enforcing SSO](/manuals/security/for-admins/single-sign-on/connect.md#optional-enforce-sso) and enforcing sign-in are different features. The following table provides a
[Enforcing SSO](/manuals/security/for-admins/single-sign-on/connect.md#optional-enforce-sso)
and enforcing sign-in are different features. The following table provides a
description and benefits when using each feature.

| Enforcement | Description | Benefits |
Expand Down
2 changes: 1 addition & 1 deletion data/summary.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -175,7 +175,7 @@ Domain management:
subscription: [Business]
for: Administrators
Enforce sign-in:
subscription: [Business]
subscription: [Team, Business]
for: Administrators
Gated distribution:
availability: Early Access
Expand Down