diff --git a/_data/toc.yaml b/_data/toc.yaml index 6deeeae5b0..46bb9a868f 100644 --- a/_data/toc.yaml +++ b/_data/toc.yaml @@ -1546,7 +1546,7 @@ manuals: - path: /docker-hub/members/ title: Manage members - path: /docker-hub/configure-sign-in/ - title: Enforce sign in + title: Enforce sign-in - sectiontitle: Single-Sign-on section: - path: /single-sign-on/ diff --git a/desktop/get-started.md b/desktop/get-started.md index 9426dafdf4..1a1ccd3ff0 100644 --- a/desktop/get-started.md +++ b/desktop/get-started.md @@ -45,7 +45,7 @@ Once logged in, you can access your Docker Hub repositories directly from Docker Authenticated users get a higher pull rate limit compared to anonymous users. For example, if you are authenticated, you get 200 pulls per 6 hour period, compared to 100 pulls per 6 hour period per IP address for anonymous users. For more information, see [Download rate limit](../docker-hub/download-rate-limit.md). -In large enterprises where admin access is restricted, administrators can create a registry.json file and deploy it to the developers’ machines using a device management software as part of the Docker Desktop installation process. Enforcing developers to authenticate through Docker Desktop also allows administrators to set up guardrails using features such as [Image Access Management](../docker-hub/image-access-management.md) which allows team members to only have access to Trusted Content on Docker Hub, and pull only from the specified categories of images. For more information, see [Configure registry.json to enforce sign in](../docker-hub/configure-sign-in.md). +In large enterprises where admin access is restricted, administrators can create a registry.json file and deploy it to the developers’ machines using a device management software as part of the Docker Desktop installation process. Enforcing developers to authenticate through Docker Desktop also allows administrators to set up guardrails using features such as [Image Access Management](../docker-hub/image-access-management.md) which allows team members to only have access to Trusted Content on Docker Hub, and pull only from the specified categories of images. For more information, see [Configure registry.json to enforce sign-in](../docker-hub/configure-sign-in.md). ### Two-factor authentication diff --git a/docker-hub/configure-sign-in.md b/docker-hub/configure-sign-in.md index c4ae6dc1ab..354534467b 100644 --- a/docker-hub/configure-sign-in.md +++ b/docker-hub/configure-sign-in.md @@ -1,7 +1,7 @@ --- description: Configure registry.json to enforce users to sign into Docker Desktop keywords: authentication, registry.json, configure, -title: Configure registry.json to enforce sign in +title: Configure registry.json to enforce sign-in --- By default, members of your organization can use Docker Desktop on their machines without signing in to any Docker account. To ensure that a user signs in to a Docker account that is a member of your organization and that the diff --git a/docker-hub/onboard-business.md b/docker-hub/onboard-business.md index 9397a932f3..75c69cc0e3 100644 --- a/docker-hub/onboard-business.md +++ b/docker-hub/onboard-business.md @@ -58,10 +58,10 @@ Now that you have a Docker Business organization, it's time to start adding memb > Before you invite members, you must create at least one team. For details, see [Create a team](../docker-hub/orgs.md/#create-a-team){: target="_blank" rel="noopener" class="_"}. -## Step 4: Enforce sign in for Docker Desktop +## Step 4: Enforce sign-in for Docker Desktop By default, members of your organization can use Docker Desktop on their machines without signing in to any Docker account. To ensure that a user signs in to a Docker account that is a member of your organization and that the -organization’s settings apply to the user’s session, you can use a `registry.json` file. For details, see [Configure registry.json to enforce sign in](../docker-hub/configure-sign-in.md){: target="_blank" rel="noopener" class="_"}. +organization’s settings apply to the user’s session, you can use a `registry.json` file. For details, see [Configure registry.json to enforce sign-in](../docker-hub/configure-sign-in.md){: target="_blank" rel="noopener" class="_"}. ## What's next diff --git a/docker-hub/onboarding-faqs.md b/docker-hub/onboarding-faqs.md index 8418b5af72..7c9d4b9db2 100644 --- a/docker-hub/onboarding-faqs.md +++ b/docker-hub/onboarding-faqs.md @@ -70,7 +70,7 @@ No. Organization owners can invite users through email and also choose a team fo ### Can I force my organization's members to authenticate before using Docker Desktop and are there any benefits? -Yes. You can [enforce sign in](../docker-hub/configure-sign-in.md) and some benefits are: +Yes. You can [enforce sign-in](../docker-hub/configure-sign-in.md) and some benefits are: - Administrators can enforce features like [Image Access Management](../docker-hub/image-access-management.md) and [Registry Access Management](../docker-hub/registry-access-management.md). - Administrators can ensure compliance by blocking Docker Desktop usage for users who do not sign in as members of the organization.