Skip to content
2 changes: 1 addition & 1 deletion content/manuals/admin/organization/general-settings.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ select your organization from the top-left account drop-down.

After configuring your organization information, you can:

- [Configure single sign-on (SSO)](/manuals/enterprise/security/single-sign-on/configure.md)
- [Configure single sign-on (SSO)](/manuals/enterprise/security/single-sign-on/connect.md)
- [Set up SCIM provisioning](/manuals/enterprise/security/provisioning/scim.md)
- [Manage domains](/manuals/enterprise/security/domain-management.md)
- [Create a company](new-company.md)
2 changes: 1 addition & 1 deletion content/manuals/admin/organization/onboard.md
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,7 @@ subscription, see [Change your subscription](/manuals/subscription/change.md).
Use your identity provider (IdP) to manage members and provision them to Docker
automatically via SSO and SCIM. See the following for more details:

- [Configure SSO](/manuals/enterprise/security/single-sign-on/configure.md)
- [Configure SSO](/manuals/enterprise/security/single-sign-on/connect.md)
to authenticate and add members when they sign in to Docker through your
identity provider.
- Optional.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Desktop settings reporting tracks user compliance with Docker Desktop settings p
Before you can use Docker Desktop settings reporting, make sure you have:

- [Docker Desktop 4.37.1 or later](/manuals/desktop/release-notes.md) installed across your organization
- [A verified domain](/manuals/enterprise/security/single-sign-on/configure.md#step-one-add-and-verify-your-domain)
- [A verified domain](/manuals/enterprise/security/single-sign-on/connect.md)
- [Enforced sign-in](/manuals/enterprise/security/enforce-sign-in/_index.md) for your organization
- A Docker Business subscription
- At least one settings policy configured
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Use the Docker Admin Console to create and manage settings policies for Docker D
Before you begin, make sure you have:

- [Docker Desktop 4.37.1 or later](/manuals/desktop/release-notes.md) installed
- [A verified domain](/manuals/enterprise/security/single-sign-on/configure.md#step-one-add-and-verify-your-domain)
- [A verified domain](/manuals/enterprise/security/single-sign-on/connect.md#step-one-add-and-verify-your-domain)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ISSUE: Broken link anchor

The link points to connect.md#step-one-add-and-verify-your-domain but this anchor doesn't exist in the new connect.md file. The heading in connect.md is now ### Step 1: Add a domain which generates the anchor #step-1-add-a-domain.

Suggested fix:

- [A verified domain](/manuals/enterprise/security/single-sign-on/connect.md#step-1-add-a-domain)

Or remove the anchor to link to the top of the page:

- [A verified domain](/manuals/enterprise/security/single-sign-on/connect.md)

- [Enforced sign-in](/manuals/enterprise/security/enforce-sign-in/_index.md) for your organization
- A Docker Business subscription

Expand Down
2 changes: 1 addition & 1 deletion content/manuals/enterprise/security/provisioning/scim.md
Original file line number Diff line number Diff line change
Expand Up @@ -227,7 +227,7 @@ This value is required in your identity provider when creating custom SCIM attri

### Step one: Set up role mapping in Okta

1. Setup [SSO](../single-sign-on/configure/_index.md) and SCIM first.
1. Setup [SSO](../single-sign-on/connect.md) and SCIM first.
1. In the Okta admin portal, go to **Directory**, select **Profile Editor**,
and then **User (Default)**.
1. Select **Add Attribute** and configure the values for the role, organization,
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -2,4 +2,5 @@
build:
render: never
title: FAQs
weight: 3
---
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ Yes, you can convert existing users to SSO accounts. Ensure users have:
- Personal access tokens created to replace passwords for CLI access
- CI/CD pipelines updated to use PATs instead of passwords

For detailed instructions, see [Configure single sign-on](/manuals/enterprise/security/single-sign-on/configure.md).
For detailed instructions, see [Configure single sign-on](/manuals/enterprise/security/single-sign-on/connect.md).

## Is Docker SSO fully synced with the IdP?

Expand Down
16 changes: 2 additions & 14 deletions content/manuals/enterprise/security/single-sign-on/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Docker Hub, Docker Desktop, and your IdP.

To configure SSO in Docker, follow these steps:

1. [Configure your domain](configure.md) by creating and verifying it.
1. [Configure your domain](connect.md) by creating and verifying it.
1. [Create your SSO connection](connect.md) in Docker and your IdP.
1. Link Docker to your identity provider.
1. Test your SSO connection.
Expand All @@ -46,18 +46,6 @@ Once configuration is complete, users can sign in to Docker services using
their company email address. After signing in, users are added to your company,
assigned to an organization, and added to a team.

## Prerequisites

Before you begin, make sure the following conditions are met:

- Notify your company about the upcoming SSO sign-in process.
- Ensure all users have Docker Desktop version 4.42 or later installed.
- Confirm that each Docker user has a valid IdP account using the same
email address as their Unique Primary Identifier (UPN).
- If you plan to [enforce SSO](/manuals/enterprise/security/single-sign-on/connect.md#optional-enforce-sso),
users accessing Docker through the CLI must [create a personal access token (PAT)](/docker-hub/access-tokens/). The PAT replaces their username and password for authentication.
- Ensure CI/CD pipelines use PATs or OATs instead of passwords.

> [!IMPORTANT]
>
> Docker plans to deprecate CLI password-based sign-in in future releases.
Expand All @@ -66,6 +54,6 @@ Using a PAT ensures continued CLI access. For more information, see the

## Next steps

- Start [configuring SSO](configure.md).
- Start [configuring SSO](connect.md).
- Read the [FAQs](/manuals/enterprise/security/single-sign-on/faqs/general.md).
- [Troubleshoot](/manuals/enterprise/troubleshoot/troubleshoot-sso.md) SSO issues.
83 changes: 0 additions & 83 deletions content/manuals/enterprise/security/single-sign-on/configure.md

This file was deleted.

Loading