Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

Are there any plans to improve Hydra client lifecycle management? For example the `client_secret_expires_at` field which is unused currently (<https://github.com/ory/hydra/issues/778|github.com/ory/hydra/issues/778>)

Hey <@U087L3FF998>
Graceful OAuth2 client secret rotation is implemented and available today in Ory Network and Ory Enterprise License, starting with Hydra v26.3.4:
_<https://www.ory.com/docs/hydra/guides/oauth2-clients#rotate-oauth2-client-secret|ory.com/docs/hydra/guides/oauth2-clients#…>_
If you're self-hosting OSS Hydra today, the available path is still to update the client secret directly.
If zero-downtime rotation is a requirement for you, happy to point you at the right people to talk about Ory Network or OEL, or just answer questions about the behaviour here.