Skip to content

docs(server): say only URI name constraints confine a URI SAN - #882

Merged
osanderson merged 1 commit into
mainfrom
docs/attester-uri-name-constraints
Nov 19, 2026
Merged

osanderson merged 1 commit into
mainfrom
docs/attester-uri-name-constraints

Conversation

@osanderson

Copy link
Copy Markdown
Collaborator

AttesterIssuerInCertificate binds an attester by a URI SAN equal to the client's ExpectedAttesterIssuer. Its doc said that, under shared anchors, an attester could name another one only through a CA under the anchors, "or an intermediate without name constraints". That reads as if any name constraint closes the gap.

It doesn't. RFC 5280 §4.2.1.10 applies each constraint type to names of its own type only, and crypto/x509 follows it. So a sub-CA constrained to the dNSName attester-a.example can still certify https://attester-b.example. A deployer who puts DNS constraints on each attester's CA in a shared pool and picks this mode lets one attester authenticate as another's clients.

Change

  • AttesterIssuerInCertificate doc: only uniformResourceIdentifier constraints, on the attester's CA or one above it, confine a URI SAN, and then only its host. It still recommends AttesterIssuerBoundToAnchor for shared trust lists.
  • ClientAuthMethodTLSClientAuthSANURI doc: one added sentence saying the same applies to shared client CAs.
  • Test: TestX5CAttesterChainIssuerInCertificateNameConstraints uses a shared anchor, where attester A's CA issues a certificate naming the client's attester:
    • with a dNSName constraint for A's host, the request is accepted;
    • with a uniformResourceIdentifier constraint for A's host, it is refused with invalid_client.

No behaviour change.

🤖 Generated with Claude Code

AttesterIssuerInCertificate's doc said an attester could name another
only through a CA under the anchors "or an intermediate without name
constraints", which reads as if any name constraint closes the gap.
RFC 5280 §4.2.1.10 applies each constraint to names of its own type,
and crypto/x509 follows it: a CA constrained to the dNSName
attester-a.example can still certify https://attester-b.example. Only
uniformResourceIdentifier constraints confine a URI SAN, and then only
its host.

The doc now says so, and ClientAuthMethodTLSClientAuthSANURI notes the
same for shared client CAs. A test pins the behaviour: under a shared
anchor, attester A's dNSName-constrained CA attests for another
attester's client, and a uniformResourceIdentifier constraint refuses
it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@codecov

codecov Bot commented Nov 19, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@sonarqubecloud

Copy link
Copy Markdown

@osanderson
osanderson merged commit 5488e4b into main Nov 19, 2026
33 checks passed
@osanderson
osanderson deleted the docs/attester-uri-name-constraints branch November 19, 2026 09:52
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.

1 participant