Skip to content

Clarify SCO trust anchors and certificate ordering - #1225

Open
madamsJuniper wants to merge 1 commit into
masterfrom
sco-trust-anchor-and-certificate-chain
Open

Clarify SCO trust anchors and certificate ordering#1225
madamsJuniper wants to merge 1 commit into
masterfrom
sco-trust-anchor-and-certificate-chain

Conversation

@madamsJuniper

@madamsJuniper madamsJuniper commented Oct 29, 2026

Copy link
Copy Markdown
Contributor

Clarifies SCO certificate configuration in response to customer confusion about certificate bundle ordering.

  • Distinguishes the trust anchor delivered through the SCO onboarding token from the conductor’s identity chain.
  • Documents the recommended identity-file ordering: leaf followed by issuing intermediates, excluding the trust anchor.
  • Explains that configuration-time property checks do not establish chain trust or successful onboarding.
  • Adds complete configuration examples and documents SCO’s file-reference requirements and single-anchor limitation.
  • Corrects certificate field naming, removes CA private-key provisioning instructions, and distinguishes SCO from ESKM certificate procedures.
@madamsJuniper
madamsJuniper marked this pull request as ready for review October 29, 2026 16:15

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

4 participants

@madamsJuniper @MichaelBaj @BenMatase @Chr1st0ph3rTurn3r