From 49c1029b291acd1dfdc32290903c6fbe62c392dd Mon Sep 17 00:00:00 2001 From: Jerae Duffin Date: Fri, 14 Jan 2022 15:48:56 -0600 Subject: [PATCH 1/2] updated registryjson link --- single-sign-on/faqs.md | 2 +- single-sign-on/index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/single-sign-on/faqs.md b/single-sign-on/faqs.md index 416efd632a..94d22b0ac0 100644 --- a/single-sign-on/faqs.md +++ b/single-sign-on/faqs.md @@ -73,7 +73,7 @@ When SSO is enforced, password-based authentication no longer works on your auto ### Q: Do I need a specific version of Docker Desktop for SSO? -Yes, all users in your organization must upgrade to Docker Desktop version 4.4.0 or higher. Users on older versions of Docker Desktop will not be able to sign in after enforcing SSO. +Yes, all users in your organization must upgrade to Docker Desktop version 4.4.2 or higher. Users on older versions of Docker Desktop will not be able to sign in after enforcing SSO. ### Q: Does SAML authentication require additional attributes? diff --git a/single-sign-on/index.md b/single-sign-on/index.md index 13e15d6804..377e2c10de 100644 --- a/single-sign-on/index.md +++ b/single-sign-on/index.md @@ -126,7 +126,7 @@ After you’ve completed the SSO configuration process in Docker Hub, you can te Before you enforce SSO in Docker Hub, you must complete the following: Test SSO by logging in and out successfully, confirm that all members in your org have upgraded to Docker Desktop version 4.4.2, PATs are created for each member, CI/CD passwords are converted to PAT. Also, when using Docker partner products (for example, VS Code), you must use a PAT when you enforce SSO. For your service accounts add your additional domains in **Add Domains** or enable the accounts in your IdP. -Admins can force users to authenticate with Docker Desktop by provisioning a registry.json configuration file. The registry.json file will force users to authenticate as a user that is configured in the allowedOrgs list in the registry.json file. For info on how to configure a registry.json file see Configure registry.json. +Admins can force users to authenticate with Docker Desktop by provisioning a registry.json configuration file. The registry.json file will force users to authenticate as a user that is configured in the allowedOrgs list in the registry.json file. For info on how to configure a registry.json file see [Configure registry.json](../docker-hub/image-access-management/#enforce-authentication.md) 1. On the Single Sign-On page in Docker Hub, click **Turn ON Enforcement** to enable your SSO. 2. When SSO is enforced, your members are unable to modify their email address and password, convert a user account to an organization, or set up 2FA through Docker Hub. You must enable 2FA through your IdP. From 84aa7886201fdc74d03157c1ccbfb57f01003199 Mon Sep 17 00:00:00 2001 From: jerae-duffin <83294991+jerae-duffin@users.noreply.github.com> Date: Tue, 18 Jan 2022 09:34:11 -0600 Subject: [PATCH 2/2] Update single-sign-on/index.md Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com> --- single-sign-on/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/single-sign-on/index.md b/single-sign-on/index.md index 377e2c10de..9455ec298c 100644 --- a/single-sign-on/index.md +++ b/single-sign-on/index.md @@ -126,7 +126,7 @@ After you’ve completed the SSO configuration process in Docker Hub, you can te Before you enforce SSO in Docker Hub, you must complete the following: Test SSO by logging in and out successfully, confirm that all members in your org have upgraded to Docker Desktop version 4.4.2, PATs are created for each member, CI/CD passwords are converted to PAT. Also, when using Docker partner products (for example, VS Code), you must use a PAT when you enforce SSO. For your service accounts add your additional domains in **Add Domains** or enable the accounts in your IdP. -Admins can force users to authenticate with Docker Desktop by provisioning a registry.json configuration file. The registry.json file will force users to authenticate as a user that is configured in the allowedOrgs list in the registry.json file. For info on how to configure a registry.json file see [Configure registry.json](../docker-hub/image-access-management/#enforce-authentication.md) +Admins can force users to authenticate with Docker Desktop by provisioning a registry.json configuration file. The registry.json file will force users to authenticate as a user that is configured in the allowedOrgs list in the registry.json file. For info on how to configure a registry.json file see [Configure registry.json](../docker-hub/image-access-management.md#enforce-authentication) 1. On the Single Sign-On page in Docker Hub, click **Turn ON Enforcement** to enable your SSO. 2. When SSO is enforced, your members are unable to modify their email address and password, convert a user account to an organization, or set up 2FA through Docker Hub. You must enable 2FA through your IdP.