SSO doc updates (#24129)

This PR updates SSO documentation to address inconsistencies, per tech
support's jira ticket. I've made some additional changes as well:

- I've removed 4/5ish call outs throughout the doc. Callouts lose
effectiveness if you use them often.
- I've condensed certain redundant UI steps like "Save", "Finish",
"Select X" and created more compound steps. This shortens the procedures
and simplifies the ~weight of each substep.
- Merged Configure and Connect docs into one. Having 1 doc for two steps
when they're necessary for the overall action risks losing users and
adding confusion.
- I've added Prerequisites from the index page to the actual procedures.
Prereqs should always be associated closely with the action users are
taking after establishing those pre-requisites.

---------

Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com>

Author: akristen

content/manuals/admin/organization/general-settings.md

@@ -29,7 +29,7 @@ To edit this information:
 
 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](/manuals/admin/company/new-company.md)

content/manuals/admin/organization/onboard.md

@@ -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.

content/manuals/enterprise/security/hardened-desktop/settings-management/compliance-reporting.md

@@ -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

content/manuals/enterprise/security/hardened-desktop/settings-management/configure-admin-console.md

@@ -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](/enterprise/security/single-sign-on/connect/#step-1-add-a-domain)
 - [Enforced sign-in](/manuals/enterprise/security/enforce-sign-in/_index.md) for your organization
 - A Docker Business subscription
 

content/manuals/enterprise/security/provisioning/scim.md

@@ -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,

content/manuals/enterprise/security/single-sign-on/FAQs/_index.md

@@ -2,4 +2,5 @@
 build:
   render: never
 title: FAQs
+weight: 40
 ---

content/manuals/enterprise/security/single-sign-on/FAQs/users-faqs.md

@@ -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?
 

content/manuals/enterprise/security/single-sign-on/_index.md

@@ -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.
@@ -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.
@@ -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.