0.4.2-alpha.2

v0.4.2-alpha.2

travis: resolve issues with autodeploy

0.4.2-alpha.1

v0.4.2-alpha.1

travis: resolve deploy issues

0.4.2-alpha

Ignore this release.

0.4.1

This release resolves an issue with the hydra token user flow.

0.4.0

This release resolves various issues, including:

• warden: token introspection is urlencoded, not json #199
• warden: move IntrospectToken from warden sdk to oauth2 #201
• warden: rename InspectToken to IntrospectToken #200
• oauth2: introspection should return custom session values #205
• oauth2: consent strategy should use at_ext for access token session data #198
• docs: move docs from gitbook to github #204

This release contains backwards incompatibilities in the Warden SDK. There are no breaks to be expected with the database backend or any HTTP endpoints.

0.3.1

This release resolves issues with rethinkdb.

0.3.0

This release resolves issues around rfc7591 and system secret generation.

This release introduces the following breaking changes:

• The system secret is now generated correctly. This will break your JWK store in RethinkDB. You will probably need to remove the jwk table from RethinkDB. Hydra will generate all required keys itself, next time you start a hydra instance.
• The client HTTP API now takes scope string instead of scopes []string. Example: { "scope": "photos openid email" }. This change affects RethinkDB as well
• hydra.Client.Scopes is now hydra.Client.Scope

0.2.0

This release focuses on resolving issues and improving the way hydra integrates by providing new and better warden endpoints, OAuth2 introspection and better consent workflow.

This release introduced a few BC breaks which can be viewed here

0.1-beta.4

This release resolves some issues when dealing with the http OAuth2 client api

0.1-beta.3

This release resolves some minor issues and improves the build stability by opting for versioned vendoring.