[docs-scanner] SSO setup steps mismatch between overview and procedure
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 92/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- docker
- Domain
- documentation
Research direction
Start with content/manuals/security/authentication/single-sign-on/_index.md and compare its “Set up SSO” list with connect.md. Update the overview to reflect the six procedure steps, then present provisioning, enforcement, and management as post-setup tasks rather than numbered setup steps.
Written by the indexing model from the issue text.
Description
File: content/manuals/security/authentication/single-sign-on/_index.md
Issue
The "Set up SSO" section in the overview lists steps that don't match the actual procedure in connect.md:
Overview (_index.md) lists:
- Configure your domain by creating and verifying it.
- Create your SSO connection in Docker and your IdP.
- Link Docker to your identity provider.
- Test your SSO connection.
- Provision users in Docker.
- Optional. Enforce sign-in.
- Manage your SSO configuration.
But the actual procedure in connect.md has:
- Step 1: Add a domain
- Step 2: Verify your domain
- Step 3: Create an SSO connection in Docker
- Step 4: Create an SSO connection in your IdP
- Step 5: Connect Docker to your IdP
- Step 6: Test the connection
Why this matters
Readers following the overview expect 7 steps but the actual guide has 6 steps with different groupings. The overview mentions "Provision users in Docker" as step 5, but this isn't part of the core setup procedure in connect.md (it's mentioned in "Next steps" instead). The overview's step 3 "Link Docker to your identity provider" is actually covered by steps 4-5 in the real procedure. This mismatch would confuse readers trying to understand what the setup process involves.
Suggested fix
Update the overview in _index.md to accurately reflect the actual steps in connect.md:
- Add a domain
- Verify your domain
- Create an SSO connection in Docker
- Create an SSO connection in your IdP
- Connect Docker to your IdP
- Test the connection
Then mention provisioning, enforcement, and management as post-setup tasks rather than numbered setup steps.
Found by nightly documentation quality scanner
- Dominant language
- Markdown
- Stars
- 4.7k
- Forks
- 8.5k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 104
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from docker/docs
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
status/triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area/dhi status/triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agilepathway/label-checker#640 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BasedHardware/omi#15662 · 1 comment ·
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
amponce/archive-movie-browser#167 ·
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·