v26.4.21
v26.4.21
Match opaque audience URIs exactly
Ory Hydra now compares a requested audience that is an opaque URI, such as a URN like urn:example:service-a, against the OAuth
2.0 client's audience allow list as a whole string. Audiences that are URLs with a host, such as
https://api.example.com/users, keep the existing path prefix matching.
The rule applies wherever audiences are validated: the audience parameter at /oauth2/auth, the client credentials and resource
owner password grants at /oauth2/token, and the revalidation of requested and granted audiences on token refresh.
Breaking changes
- A request for an opaque audience that is not listed verbatim in the client's
audienceallow list fails withinvalid_request. This includes values that differ only by a suffix or trailing slash, such as requestingurn:example:service-a:childorurn:example:service-a/when the allow list containsurn:example:service-a. - Refreshing a token whose requested and granted audience is an opaque URI fails with
invalid_requestuntil the client'saudienceallow list contains that value verbatim.
Add every opaque audience your clients request to the client's audience allow list exactly as it is requested. Clients whose
allow list contains only URLs with a host are not affected.
Ory Console Lite runs on a read-only root file system
The Ory Console Lite container runs on a read-only root file system, and you can reach it through kubectl port-forward. It
listens on HOSTNAME=0.0.0.0 by default. If you run Ory Console Lite with host networking, set HOSTNAME=127.0.0.1 so that it
listens on the loopback interface only.