Skip to content

docs: describe did:x509 validation, link the wiki for certificate use in use cases - #4680

Open
reinkrul wants to merge 2 commits into
docs/rtd-move-oauthfrom
docs/rtd-move-certificates
Open

reinkrul wants to merge 2 commits into
docs/rtd-move-oauthfrom
docs/rtd-move-certificates

Conversation

@reinkrul

@reinkrul reinkrul commented Nov 5, 2026 •

Copy link
Copy Markdown
Member

Part of the Read the Docs → wiki move (stacked on #4679).

deployment/certificates.rst, did:x509 section, after review:

  • keeps the explanation of what did:x509 is and how it differs from connection certificates
  • adds how the node validates a did:x509 DID: chain from the credential's x5c header, validated using only that chain; the DID's CA fingerprint must match a CA in the chain; the other DID fields (san, subject) must match the leaf; the TLS trust store and OS CA bundle are not used
  • the trust sentence now says how use cases set it: presentation definitions only accept did:x509 DIDs with a specific CA fingerprint
  • links the wiki pages on how use cases use certificates (UZI certificates as a source of identity, X509Credential with UZI server certificates)

The CRL, pki.* and algorithm text is unchanged.

Assisted by AI

@reinkrul
reinkrul added this pull request to stack #4674 November 5, 2026 09:09
@reinkrul
reinkrul marked this pull request as ready for review November 5, 2026 09:30
@reinkrul
reinkrul force-pushed the docs/rtd-move-certificates branch 5 times, most recently from 3c50796 to faa6f10 Compare November 6, 2026 12:19
@reinkrul reinkrul changed the title docs: move did:x509 background to the wiki docs: describe did:x509 validation, link the wiki for certificate use in use cases Nov 6, 2026
@reinkrul
reinkrul force-pushed the docs/rtd-move-certificates branch from 0d69e70 to 2862456 Compare November 6, 2026 13:07
@reinkrul
reinkrul force-pushed the docs/rtd-move-certificates branch from 2862456 to 73bb0b0 Compare November 6, 2026 15:57

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants