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

Skip to main content

v26.4.21

v26.4.21​

A login continued with code_hint needs client credentials at the token endpoint​

An application can continue an IdP-initiated login by sending the authorization code it received as code_hint to /api/oauth/authorize. Ory Polis then issues a new code without another round trip to the identity provider.

Exchanging that new code at /api/oauth/token now requires the client to authenticate, as exchanging the IdP-initiated code itself does. A request with a PKCE code_verifier but no valid client_id and client_secret is answered with status 401 and invalid_client. PKCE is still checked when the authorize request carried a code_challenge.

Breaking change​

If your application continues IdP-initiated logins with code_hint and exchanges the code with a code_verifier alone, send its client_id and client_secret as well. An application that uses the tenant=...&product=... or dummy client ID sends the value of CLIENT_SECRET_VERIFIER as the secret.

Ory Kratos already sends its client credentials and needs no change.

SCIM user PATCH rejects a path that indexes past the end of an attribute​

A SCIM PATCH on a user can name an entry of a multi-valued attribute by its position, for example emails[1].value. Polis accepted any position, and a position past the end of the attribute left empty entries before it.

A path may now name an entry the attribute has, or the next one, which adds an entry. Any other position fails the request with status 400 and scimType invalidPath, and none of the request's operations are applied. The same applies to a path that names anything other than a position on a multi-valued attribute, such as emails.length.

Paths that select an entry by a filter, such as emails[type eq "work"].value, are not affected. Okta and Microsoft Entra ID use this form.

If you run your own SCIM client and it addresses entries by position, make sure it does not skip positions.