Skip to content

Commit 36aa055

Browse files
enforce sign in vs enforce sso update (#20794)
Signed-off-by: Craig Osterhout <[email protected]>
1 parent 654e871 commit 36aa055

File tree

2 files changed

+20
-8
lines changed

2 files changed

+20
-8
lines changed

content/admin/organization/onboard.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,13 @@ Configuring SSO and SCIM is optional and only available to Docker Business subsc
6767

6868
You can manage your members in your identity provider and automatically provision them to your Docker organization with SSO and SCIM. See the following for more details.
6969
- [Configure SSO](/security/for-admins/single-sign-on/) to authenticate and add members when they sign in to Docker through your identity provider.
70-
- Optional: [Enforce SSO](/security/for-admins/single-sign-on/connect/#optional-enforce-sso) to ensure that users must sign in to Docker with SSO.
70+
- Optional: [Enforce SSO](/security/for-admins/single-sign-on/connect/#optional-enforce-sso) to ensure that when users sign in to Docker, they must use SSO.
71+
> [!NOTE]
72+
>
73+
> Enforcing single sign-on (SSO) and [Step 5: Enforce sign-in for Docker
74+
> Desktop](#step-5-enforce-sign-in-for-docker-desktop) are different
75+
> features. For more details, see
76+
> [Enforcing sign-in versus enforcing single sign-on (SSO)](/security/for-admins/enforce-sign-in/#enforcing-sign-in-versus-enforcing-single-sign-on-sso).
7177
- [Configure SCIM](/security/for-admins/provisioning/scim/) to automatically provision, add, and de-provision members to Docker through your identity provider.
7278

7379
## Step 5: Enforce sign-in for Docker Desktop

content/security/for-admins/enforce-sign-in/_index.md

Lines changed: 13 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -35,10 +35,16 @@ following occurs:
3535
- When a user signs out, the **Sign in required!** prompt appears and they can
3636
no longer use Docker Desktop.
3737

38-
> **Enforce sign-in versus enforce SSO**
39-
>
40-
> Enforcing sign-in ensures that users are required to sign in to use Docker Desktop.
41-
> If your organization is also using single sign-on (SSO), you can optionally enforce SSO.
42-
> This means that your users must use SSO to sign in, instead of a username and password.
43-
> When you enforce sign-in and enforce SSO, your users must sign in and must use SSO to do so.
44-
> See [Enforce SSO](/security/for-admins/single-sign-on/connect#optional-enforce-sso) for details on how to enable this for your SSO connection.
38+
## Enforcing sign-in versus enforcing single sign-on (SSO)
39+
40+
[Enforcing
41+
SSO](/security/for-admins/single-sign-on/connect#optional-enforce-sso) and
42+
enforcing sign-in are different features. The following table provides a
43+
description and benefits when using each feature.
44+
45+
| Enforcement | Description | Benefits |
46+
|:----------------------------------|:----------------------------------------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
47+
| Enforce sign-in only | Users must sign in before using Docker Desktop. | Ensures users receive the benefits of your subscription and ensures security features are applied. In addition, you gain insights into users’ activity. |
48+
| Enforce single sign-on (SSO) only | If users sign in, they must sign in using SSO. | Centralizes authentication and enforces unified policies set by the identity provider. |
49+
| Enforce both | Users must sign in using SSO before using Docker Desktop. | Ensures users receive the benefits of your subscription and ensures security features are applied. In addition, you gain insights into users’ activity. Finally, it centralizes authentication and enforces unified policies set by the identity provider. |
50+
| Enforce neither | If users sign in, they can use SSO or their Docker credentials. | Allows users to access Docker Desktop without barriers, but at the cost of reduced security and insights. |

0 commit comments

Comments
 (0)