You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wire CIMD config through embedded AS and enable storage decorator
Phase 2 PR 3 — config threading and server wiring.
Config chain: RunConfig.CIMD → Config.CIMD* → AuthorizationServerParams
→ AuthorizationServerConfig → discovery handler.
Changes:
- config.go: add CIMDRunConfig struct and CIMD* fields to Config;
defaults (256 entries, 5 min fallback TTL) applied in applyDefaults();
validation (cacheMaxSize >= 1 when enabled) in Validate()
- runner/embeddedauthserver.go: add resolveCIMDConfig helper to unpack
nullable *CIMDRunConfig; populate Config.CIMD* from RunConfig.CIMD
- server/provider.go: add CIMDEnabled to AuthorizationServerParams and
AuthorizationServerConfig; wire through NewAuthorizationServerConfig
- server_impl.go: wrap storage with CIMDStorageDecorator when enabled
(after legacy migration, before createProvider — decorator must be in
place before fosite holds a reference to the storage instance);
pass CIMDEnabled to AuthorizationServerParams
- server/handlers/discovery.go: set ClientIDMetadataDocumentSupported
in buildOAuthMetadata() — both OAuth AS and OIDC discovery endpoints
advertise CIMD support when enabled
CIMD is opt-in (disabled by default) to avoid introducing outbound
HTTPS fetching in existing deployments without explicit operator action.
Relates to #4825
Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
0 commit comments