Ory Hydra serves as an open-source OAuth 2.0 server and OpenID Connect provider designed to handle token issuance, validation, client application registration, and cryptographic key management. By design, the software does not store user credentials, such as usernames or passwords, allowing organizations to maintain their existing identity management infrastructure. This architecture offloads the complex requirements of the OAuth specifications, which span hundreds of pages, to a centralized server that can be deployed on an organization's own infrastructure.
The OpenID Foundation has officially certified Hydra version 1.0.0 as an OpenID Provider. This certification covers the Basic, Implicit, Hybrid, Config, and Dynamic profiles when the software is utilized alongside Ory’s reference login application. The server functions by redirecting authentication requests to a designated login and consent application, which verifies user credentials against an external store—such as Ory Kratos or a custom-built system—before informing Hydra of the user's identity and the scope of data they have authorized for sharing.
Hydra supports several critical security flows, including the authorization code flow with Proof Key for Code Exchange (PKCE). This specific extension is intended to mitigate risks associated with intercepted codes in mobile and single-page application environments. Additionally, the server accommodates machine-to-machine traffic via client credentials, supports refresh tokens, and facilitates the device authorization flow commonly used by command-line interfaces and smart television applications.
For security and lifecycle management, access tokens issued by Hydra are opaque by default and can be revoked immediately upon request. Other services within an ecosystem can verify the status of these tokens using the introspection method defined in RFC 7662. Furthermore, the platform supports dynamic client registration, allowing client applications to register themselves programmatically.
Regarding deployment, the software is compatible with Linux, macOS, Windows, Docker, and Kubernetes environments. For production use, the system requires PostgreSQL version 12 or later, MySQL version 8 or later, or CockroachDB. SQLite is supported only for local development purposes. By default, the software transmits anonymized and summarized telemetry data, though administrators have the option to disable this feature. The source code remains available for public access and deployment via GitHub.





