This release adds a standard OpenID Connect Discovery endpoint to the authentication layer. OIDC relying parties read the discovery document to learn the platform's authorization, token and key endpoints and its supported capabilities, removing the need to configure each URL by hand. Alongside it, OAuth token request outcomes are now logged, giving operators a record of which token exchanges succeeded and which failed.
OpenID Connect Discovery
- Self-describing metadata. The discovery document publishes the issuer, the authorization and token endpoints, the key-set location, and the supported grant and response types at a well-known path.
- Zero-touch client configuration. A conforming OIDC client points at the issuer and resolves the rest automatically, so onboarding a new identity consumer does not require manual endpoint entry.
Token request logging
- Outcome visibility. Each token request records whether it succeeded or failed, so an operator can distinguish a misconfigured client from a rejected credential without reproducing the flow.
Both additions build on the OAuth 2.1 authorization framework already in the platform; existing clients continue to operate unchanged, and the discovery endpoint is available immediately after upgrade.