docker / docker/docs

[docs-scanner] Contradictory SSO requirements: AI Governance vs Business subscription

Open
#26,041 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Markdown
Stars
4.7k
Forks
8.5k
Avg merge
2d 18h
Merged PRs (30d)
108

Description

File: content/manuals/accounts/organization/manage/manage-licenses.md

Issue

The documentation contradicts itself about SSO and provisioning requirements. In manage-licenses.md, it states:

AI Governance licenses include single sign-on (SSO) and provisioning features regardless of your Docker Core subscription. Automatic license assignment requires setting up SSO, then provisioning with System for Cross-domain Identity Management (SCIM) or Just-in-Time (JIT).

However, in content/manuals/security/authentication/_index.md, it clearly states:

SSO requires a Docker Business subscription.

Why this matters

Readers trying to understand whether they can use SSO with AI Governance licenses alone (without a Business subscription) will get conflicting information. This affects purchasing decisions and setup expectations. If AI Governance truly provides SSO capabilities without Business, that's a significant feature that contradicts the general authentication documentation. If it doesn't, the manage-licenses.md text is misleading.

Suggested fix

Clarify the relationship between AI Governance licenses and SSO/provisioning features. Either:

  1. If AI Governance does provide SSO without Business: Update the authentication documentation to note this exception and explain the scope/limitations
  2. If AI Governance requires Business for SSO: Remove or rephrase the claim in manage-licenses.md to clarify that SSO setup (which requires Business) is a prerequisite for automatic license assignment, not a feature included with AI Governance

The text should make clear what subscription tier is actually required for SSO when using AI Governance.


Found by nightly documentation quality scanner

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read content/manuals/accounts/organization/manage/manage-licenses.md and content/manuals/security/authentication/_index.md, then verify the authoritative subscription requirements for SSO, SCIM, and JIT. Confirm with the documentation or product owner which wording is correct. Done means both pages consistently state the required tier and the scope of AI Governance provisioning.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
authentication, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.