Repository navigation
OpenID Connect: support Client ID Metadata Documents (CIMD) #13675
StephanMeijer
started this conversation in
Ideas
Replies: 1 comment 1 reply
|
All of the features I'm adding there will eventually make it to Authelia. I'm considering if CIMD should be added with DCR. This is because CIMD technically benefits a lot from caching the discovered details both in security and in economical use. We are also likely to add Token Exchange with ID-JAG, Transaction Tokens, and more robust Resource Indicator support in the next release though. I'm also looking into CIBA, AuthZEN, and SSF as you may have noticed; as well as On-Behalf-Of for AI Agents. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Now that authelia/oauth2-provider#863 adds Client ID Metadata Document (CIMD) support, could Authelia expose it as an opt-in setting with an allow list of client ID URLs? Scopes, grant types and the authorization policy for those clients would still come from Authelia's configuration.
Use case: I run an MCP server with Claude as the client. Today that needs a hand-made OIDC client with a hashed secret. With CIMD I could pick "Use Claude's published identity" and keep no secret at all.
CIMD keeps no stored registrations, so it fits Authelia's config-driven model better than DCR (#7304, #9898). The MCP authorization spec (revision 2026-07-28) now recommends CIMD and deprecates DCR.
AI disclosure: this text was drafted by an AI assistant (Claude) from my notes, and I reviewed it before posting. No other AI use.
All reactions