Skip to content

Add Issuer Trust to Security Considerations#254

Open
jeswr wants to merge 1 commit intomainfrom
feat/security-issuer-trust
Open

Add Issuer Trust to Security Considerations#254
jeswr wants to merge 1 commit intomainfrom
feat/security-issuer-trust

Conversation

@jeswr
Copy link
Copy Markdown
Member

@jeswr jeswr commented Apr 26, 2026

The change is small — see the diff. Bikeshed-rendered preview is not currently available for feature branches (the CI build only publishes from main).

Summary

Adds a new non-normative subsection Issuer Trust to § Security Considerations (after § Client Trust), covering two issuer-side considerations that the current text does not surface:

  • Issuer trust is unconditional. Every assertion of the user's identity comes from the issuer. The user is fully reliant on it; a compromised, malicious, or unavailable issuer can deny access, impersonate, or rewrite identity-related claims.
  • Many agents on a single issuer is a single point of failure. Concentration risk grows with the issuer's user base.

Source

Both points were raised by @csarven on solid/specification#776. Surfacing them upstream here as the appropriate home for OIDC-specific Security and Privacy Considerations.

Test plan

  • bikeshed spec (or the project's equivalent) builds without errors.
  • # Security Considerations # {#security} shows the new ## Issuer Trust ## {#security-issuer-trust} subsection between Client Trust and Privacy Considerations.
  • Anchor #security-issuer-trust resolves.

Two non-normative bullets, both raised by @csarven on solid/specification#776
(solid/specification#776 (comment)):

- Issuer trust is unconditional: a compromised / malicious / unavailable
  issuer can deny access, impersonate, or rewrite identity-related claims.
- Many agents on a single issuer is a single point of failure: concentration
  risk grows with the issuer's user base.
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