New Ory Agent Security is now live! Claim your complimentary test drive. Get Started!

Skip to main content

v26.4.20

v26.4.20​

Container images contain only the service binary​

The OEL container images of Ory Kratos Identities, Ory Hydra Authorization, Ory Keto Permissions, Ory Oathkeeper IAM Proxy, and Ory Talos Secure API Keys use an empty base image. The image contains only the service binary, which carries its own root certificates and time zone data. The images still run as user 65532. This includes the FIPS images of Ory Kratos Identities and Ory Hydra Authorization, which no longer use a Red Hat Universal Base Image. The -debug images do not change.

Breaking changes​

  • The image has no /tmp, no /etc/passwd, no /etc/group and no CA bundle file.
  • The working directory is /, and the service user cannot write to it.
  • With SQLite, use an absolute database path on a writable volume, and mount a writable /tmp.
  • To set the owner and group of a Unix socket, use numeric IDs.
  • To trust a private certificate authority, see Trust a private certificate authority.

For a shell in the container, use the -debug image tag. See Container image contents.

A consent request now has skip: true only if the remembered consent granted every requested scope and every requested access token audience. If an OAuth2 client asks for an audience value that the remembered consent did not grant, the consent request has skip: false, and your consent app shows the consent screen.

A client that requests different audiences in separate authorization requests sees the consent screen whenever it requests an audience that the most recent remembered consent did not grant. To avoid this, request every audience the client needs in one authorization request, or have your consent app include the audiences the user granted before in grant_access_token_audience. Both approaches issue access tokens that are valid for every granted audience. Where audience isolation matters, grant only the requested audiences.

Breaking changes​

A request with prompt=none for an audience that the remembered consent did not grant now fails with consent_required instead of returning an authorization code. The error description says that the remembered consent does not cover all requested scopes and audiences.

If your consent app accepts consent requests without setting grant_access_token_audience, the remembered consent grants no audience. Every later request with an audience value then shows the consent screen, and every such request with prompt=none fails. Set grant_access_token_audience to the audiences the user approved, usually requested_access_token_audience.