This list makes you aware of (breaking) changes. For patch notes, please check the releases tab.
This version adds performance metrics to /health
and sends anonymous usage statistics to our servers, click here for more
details on this feature and how to disable it.
This PR improves some performance bottlenecks, offers more control over Hydra, moves to Go 1.8, and moves the REST documentation to swagger.
Before applying this update, please make a back up of your database. Do not upgrade directly from versions below 0.7.0.
To upgrade the database schemas, please run the following commands in exactly this order
$ hydra help migrate sql
$ hydra help migrate ladon
$ hydra migrate sql mysql://...
$ hydra migrate ladon 0.6.0 mysql://...
Ladon was greatly improved with version 0.6.0, resolving various performance bottlenecks. Please read more on this release here.
Redis and RethinkDB are removed from the repository now and no longer supported, see this issue.
To reflect the GitHub organization rename, Hydra was moved from https://github.com/ory-am/hydra
to
https://github.com/ory/hydra
.
The method FindPoliciesForSubject
of the policy SDK was removed. Instead, List
was added. The HTTP endpoint GET /policies
no longer allows to query by subject.
To generate JWKs previously the payload at POST /keys
was { "alg": "...", "id": "some-id" }
. id
was changed to
kid
so this is now { "alg": "...", "kid": "some-id" }
.
SQL Migrations are no longer automatically applied. Instead you need to run hydra migrate sql
after upgrading
to a Hydra version that includes a breaking schema change.
Set the log format to json using export LOG_FORMAT=json
You can configure SQL connection limits by appending parameters max_conns
, max_idle_conns
, or max_conn_lifetime
to the DSN: postgres://foo:bar@host:port/database?max_conns=12
.
... and are swagger 2.0 spec.
Documentation on scopes (e.g. offline) was added.
Hydra now uses github.com/ory/herodot
for writing REST responses. This increases compatibility with other libraries
and resolves a few other issues.
Hydra is now capable of gracefully handling SIGINT.
Hydra now implements best practices for running HTTP servers that are exposed to the public internet.