github.com/ory/hydra

The new SameSite attribute is now enforced on Google Chrome and may cause issues with your current ORY Hydra deployment:

SameSite=None no longer works without secure flag cookies. If you are using the --dangerous-force-http flag and have not configured SameSite=Lax your users will no longer be able to perform OAuth2 flows.

The next FireFox release will follow this implementation as well. To prevent your users from experiencing issues:

• Remove --dangerous-force-http from your deployment. This flag should never be set outside of local development machines anyways!
• Set environment variable SERVE_COOKIES_SAME_SITE_MODE=Lax or configuration value serve.cookies.same_site_mode = Lax.

By applying this release, the above recommendations will be set per default, for example using Lax when --dangerous-force-http is set.

Many of you reached out in the past asking about managed / SaaS offerings from ORY, for more support, automated updates, and automated fixes for issues like the SameSite behavior above. We would like to invite those interested in that kind of an offering and service to engage in a dialogue to better help us understand how you are using ORY, what requirements your businesses have and how we can better help and service you. Together, we can shape some of this journey together. If you like to be part of this conversation please send an email to jared@ory.sh so we can get in touch directly and begin talking about what an ideal and fully supported offering from ORY would look like for you.

This patch additionally includes a breaking API change for the "Revoke Consent Sessions API endpoint" - please check the breaking changes below. Bugfixes are included in this release as well - such as pretty JSON format logging, fixes to Jaeger configuration, and more!

Breaking Changes

Previously, '/oauth2/auth/sessions/consent?subject=foo@bar.com' would revoke all consent sessions of that user. This may be problematic in cases where the caller forgot to specify the client ID as all tokens for that user are revoked. To prevent that, a "failsave" all=true is now required to make this explicit: '/oauth2/auth/sessions/consent?subject=foo@bar.com&all=true'.

Bug Fixes

• Add json_pretty to possible log.format values (cc96359)
• Add uri to jaeger's local_agent_address (#1982) (4d5df3e), closes #1956
• Bump clidoc (7800049)
• Remove duplicate html tags (#1960) (819fe6c)
• Send total item count in X-Total-Count header (#1983) (5f9f294), closes #1666
• Use SameSite=Lax for dev environments per default (534203c)
• Use SameSite=Lax for quickstart (379f5f0), closes #1988 #1981

Code Generation

• Pin v1.7.0 release commit (ff4b81e)

Code Refactoring

• Cleanup the code for CORS handling (#1959) (5a53d28), closes #1754

Documentation

• Access token time config (#1966) (f066cc1):

  Adds a short guide how to configure access token expiration time.

• Add expiry-time sidebar item (#1967) (5f8e58b):

  Adds token-expiration to sidebar.

• Add sdk samples for tls termination and tls verify skip (#1968) (6619e59)

• Add section on oauth2 limitations at beginning (4254363)

• Adopt new sidebar.json (8faf070)

• Clarify secure flag in chrome (f01ac17)

• Clarify when to use oauth2 (4c58601)

• Document SameSite woes on Chrome (921f8c2)

• Fix broken links (b3c6c5a)

• Fix invalid links (3838cdc)

• Fix typos (#1964) (83ce657)

• Fixed link (#1969) (ba1f14b)

• Update oauth2 limitation section (62e6fdf)

• Update TLS example to quote strings not spawn a subshell (#1961) (0e6ed29)

Features

• Add audit and debug logs for cookies (08813b3)

• Add clidoc task and program (e44d256)

• Revoke consent sessions of a subject only if explicitly requested (#1952) (fb925cf), closes #1951:

  This patch adds query parameter all to /oauth2/auth/sessions/consent. If all=true, then all consent sessions of a certain subject will be revoked.

Unclassified

• Add 1.5 notes to UPGRADING.md (270b89a)
• Whitelist new session cookies and set log level to trace (6e75638)