Tags: ory/hydra
Tags
We’re thrilled to announce the release of **Ory Hydra 2.3.0**! This v… …ersion comes packed with **graceful token refresh**, performance improvements, and fixes that enhance stability, reduce database load, and streamline the developer experience. We strongly recommend upgrading to take advantage of these enhancements and ensure the best possible OAuth2 and OpenID Connect experience with Ory Hydra. Thank you to everyone who contributed! Ory Hydra now supports graceful refresh token rotation, making OAuth2 and OpenID Connect refresh flows significantly more resilient in scenarios such as Single Page Apps and IoT. Even in highly distributed or concurrent environments, Hydra gracefully handles token refreshes reliably, ensuring tokens are not dropped or double-used. PRs: [#3860](#3860), [#3895](#3895) Previously, the `redirect_uri` was not required when performing flows with `scope=openid`. This release enforces the requirement to comply with the OpenID Connect standard. PR: [#3900](#3900) Hydra now supports explicit SQL migration commands **`migrate sql up|down|status`** that streamline database schema management and help with zero-downtime upgrades. PR: [#3894](#3894) - **Access token strategy & advanced CLI improvements** The CLI introduces new parameters and an option to specify a custom client ID on creation, making it easier to manage and script Hydra deployments. PRs: [#3718](#3718), [#3725](#3725), [#3874](#3874) - **Built-in login & consent UI for `hydra perform authorization-code`** A minimal built-in UI for login and consent can be enabled when testing with the CLI, removing the need to spin up a separate service. PR: [#3845](#3845) Unused indices have been removed, down migration scripts renamed for consistency, and all migrations are more efficient overall. PRs: [#3859](#3859), [#3911](#3911) - **Improve persistence logic** – Database transactions and concurrency have been improved across the authorization and token handlers. PRs: [#3756](#3756), [#3763](#3763), [#3886](#3886) - **Support for more claims in password grant** – You can now include additional claims in the password grant flow, providing extra flexibility in advanced scenarios. Only available with an Ory Enterprise License. PR: [#3864](#3864) - **Transaction Wrappers** Authorization and token issuance are now wrapped more consistently to prevent partial writes and race conditions. PRs: [#3730](#3730), [#3763](#3763) - **Improved Docker setup** Docker configurations have been refined, removing inconsistencies in the Compose setup and enabling a fully static binary build. PRs: [#3826](#3826), [#3924](#3924) - **Proper JSON round-tripping** Fixed an issue causing custom claims to break if they were nested or unexpectedly typed. JSON round-trips are now correct. PR: [#3819](#3819) - **Speed up public key retrieval** Reduced overhead for the JWK public endpoint, solving CPU contention issues in large-scale deployments. PRs: [#3787](#3787), [#3870](#3870) - **Fix Docker Compose references** The CLI now properly references `docker compose` instead of `docker-compose`, ensuring compatibility with modern Docker setups. PR: [#3815](#3815) - **Dependency upgrades** Bumped `fosite`, `ory/x`, `pgx/v5`, and various third-party libraries for improved stability and performance. - **Updated docs** Updated examples, improved JWK documentation, added notes on Docker Compose usage, and refined OpenID Connect discovery docs. - **More tracing context** Tracing calls have been consistently standardized with `otelx.End()`, and additional context ensures better observability. - **Code generation & housekeeping** Various housekeeping tasks: pinned GHA versions, fixed minor comment typos, updated newsletters/links, and more. To upgrade to 2.3.0, follow the usual steps: 1. **Back up your database** (always recommended). 2. **Update your Hydra version** in your Docker configuration, binary, or build to `v2.3.0`. 3. **Run `hydra migrate sql up`** (if using the new commands) or your usual migration procedure. 4. **Restart your services** and confirm that Hydra is up and running. Check the [migration docs](https://www.ory.sh/docs/hydra/self-hosted/upgrade) for detailed information. As always, we love hearing from our community. Here are some ways to get involved: - **Join our Slack**: [Ory Community Slack](https://www.ory.sh/chat) - **Ask questions on GitHub Discussions**: [Ory Hydra Discussions](https://github.com/ory/hydra/discussions) - **Submit bugs and feature requests**: [GitHub Issues](https://github.com/ory/hydra/issues) Thanks to all contributors for making Ory Hydra the best-in-class OAuth2 and OpenID Connect server. For Ory Hydra v2.4.0 we are looking at another highly anticipated community-contributed feature, the OAuth 2.0 Device Authorization Grant! **Full Changelog**: [v2.2.0...v2.3.0](v2.2.0...v2.3.0) *Happy building with Ory Hydra!*
 Ory Hydra, the OAuth2 and OpenID Connect server designed for web-scale deployments introduces its most advanced update with version 2.2! Want to check out Ory Hydra yourself? Try common OAuth2 flows in the [Ory OAuth2 Get Started guide](https://www.ory.sh/docs/getting-started/ory-network-oauth2)! This version significantly enhances performance, supporting six times more authorization flows than version 2.1, thanks to architectural improvements that minimize database interactions for login and consent processes. Key improvements include: - Enhanced integration with Ory Kratos, ensuring seamless synchronization of login and logout states across both services. Users logged out from Ory Hydra will automatically log out from Ory Kratos, enhancing security and user experience. - The ability to bypass the logout consent screen for specific clients, streamlining the logout process. - Simplified migration with the new feature to import OAuth2 Client IDs, making the transition to Ory Hydra smoother. - Support for the OIDC Verifiable Credentials specification, expanding the server's capabilities in identity verification. Thank all contributors who have made this release available!
This release optimizes the performance of authorization code grant fl… …ows by minimizing the number of database queries. We acheive this by storing the flow in an AEAD-encoded cookie and AEAD-encoded request parameters for the authentication and consent screens. BREAKING CHANGE: * The client that is used as part of the authorization grant flow is stored in the AEAD-encoding. Therefore, running flows will not observe updates to the client after they were started. * Because the login and consent challenge values now include the AEAD-encoded flow, their size increased to around 1kB for a flow without any metadata (and increases linearly with the amount of metadata). Please adjust your ingress / gateway accordingly.
This release optimizes the performance of authorization code grant fl… …ows by minimizing the number of database queries. We acheive this by storing the flow in an AEAD-encoded cookie and AEAD-encoded request parameters for the authentication and consent screens. BREAKING CHANGE: * The client that is used as part of the authorization grant flow is stored in the AEAD-encoding. Therefore, running flows will not observe updates to the client after they were started. * Because the login and consent challenge values now include the AEAD-encoded flow, their size increased to around 1kB for a flow without any metadata (and increases linearly with the amount of metadata). Please adjust your ingress / gateway accordingly.
We are excited to announce the next Ory Hydra release! This release i… …ncludes the following important changes: - Fixed a memory leak in the OpenTelemetry implementation, improving overall memory usage and stability. - Added a missing index for faster janitor cleanup, resulting in quicker and more efficient cleanup operations. - Fixed a bug related to SameSite in dev mode, ensuring proper functionality and consistency in handling SameSite attributes during development. We appreciate your continuous support and feedback. Please feel free to reach out to us with any further suggestions or issues.
We are excited to share this year's Q1 release of Ory Hydra: v2.1.0! Highlights: * Support for Datadog tracing (#3431). * Ability to skip consent for trusted clients (#3451). * Setting access token type in the OAuth2 Client is now possible (#3446). * Revoke login sessions by SessionID (#3450). * Session lifespan extended on session refresh (#3464). * Token request hooks added for all grant types (#3427). * Reduced SQL tracing noise (#3481). Don't want to run the upgrade yourself? Switch to [Ory Network](https://console.ory.sh/registration?flow=d1ae4761-3493-4dd9-b0ce-3200916b38aa)!
PreviousNext