Ory Hydra provides OAuth 2.0 and OpenID Connect services without storing passwords

src-f183a530

Ory Hydra is an open-source OAuth 2.0 authorization server and OpenID Connect provider designed to handle token issuance and validation while leaving user authentication to an organization’s existing identity system. It can register client applications and manage the keys used to sign tokens, but it does not store usernames or passwords.

This separation is central to Hydra’s role in an identity architecture. Organizations can keep credential verification in an existing service and connect that service to Hydra through a login and consent application. The application checks a user’s credentials against the organization’s user store, then reports the user’s identity and consent decisions to Hydra. Hydra uses that information to issue tokens to applications.

Token and client responsibilities

OAuth 2.0 and OpenID Connect define extensive requirements for authorization and identity flows. Implementing a server that conforms to those specifications can require careful handling of tokens, clients, consent and protocol behavior. Hydra supplies server-side protocol functionality, allowing teams to run it on their own infrastructure rather than build those capabilities from scratch.

The project supports several flows for different client needs. These include authorization code with Proof Key for Code Exchange (PKCE), client credentials for machine-to-machine traffic, refresh tokens and the device authorization flow used by devices such as TVs and tools such as command-line applications. PKCE adds protection against an intercepted authorization code being reused, particularly in mobile and single-page applications.

Access tokens are opaque by default, according to the project description, and Hydra can revoke a token immediately. Other services can ask whether a token remains active through introspection, a mechanism specified in RFC 7662. Hydra also supports dynamic client registration, through which client applications can register themselves.

These capabilities do not remove the need for deployment-specific security decisions. Teams still need to determine how the login and consent application connects to their identity store, which clients are permitted, and how tokens and signing keys fit into their operational controls. Because Hydra does not manage user passwords, the connected identity system remains responsible for credential checks.

Standards certification and deployment

The OpenID Foundation certified Hydra v1.0.0, running Ory’s reference login application, as an OpenID Provider across the Basic, Implicit, Hybrid, Config and Dynamic profiles. The certification applies to that version and reference application combination; it should not be read as a statement that every deployment or configuration has been independently assessed.

Hydra runs on Linux, macOS and Windows, and can also be deployed with Docker or Kubernetes. For production, the listed database options are PostgreSQL 12 or later, MySQL 8 or later, and CockroachDB. SQLite is intended for local development only. Organizations evaluating the server should account for these database requirements when planning a production deployment.

The software sends anonymized, summarized telemetry, which administrators can disable. That setting may be relevant to teams reviewing data flows and operational policies before deployment. Hydra is available as open-source software on GitHub, with no charge for running it on an organization’s own infrastructure, according to the project information.

What identity teams should assess

Hydra is best understood as an authorization and token service that works alongside, rather than replaces, an organization’s authentication system. Its separation of responsibilities can help teams retain an existing login service while adding standardized OAuth 2.0 and OpenID Connect capabilities. It also means the integration between Hydra, the login and consent application, and the user store is a key part of the overall design.

Before adopting it, identity and platform teams should map their required client flows to Hydra’s supported options, validate how token revocation and introspection will be used by connected services, and select a supported production database. They should also review client registration, signing-key management and telemetry settings as part of deployment planning. These checks help ensure that the server’s protocol capabilities align with the organization’s identity architecture and operating requirements.