v5.7.1

[panva]

Refactor

• jwt client authentication audience is now an issuer identifier string (0b05217)

Note: If needed this can be reverted using the extras.clientAssertionPayload option.

---

This discussion was created from the release v5.7.1.

[nwalters512]

@panva can you share more about the rationale for this change? Unfortunately this was very much a breaking change for us, and it's a shame to see it was released in a patch version.

From my read of the OIDC spec (https://openid.net/specs/openid-connect-core-1_0.html#rfc.section.9), under "9. Client Authentication", "private_key_jwk", aud is indeed supposed to be the "Authorization Server's Token Endpoint", not the issuer. It'd be helpful to know which part of the spec this change was based on.

[nwalters512]

It's not that simple. The specs are layered in such a way that the issuer identifier is also a valid value for an AS to accept.

I buy that; I'm definitely not very well versed in the spec, this is just what I found with a quick read. For my own edification, do you know offhand what other pieces of the spec apply here?

[panva]

I cannot say more at this time, the issue will be discussed publicly in the IETF OAuth WG interim meeting on 2025-01-27.

[nwalters512]

@panva are you able to share the relevant parts of the spec now? I'd like to forward them to platforms that my product works with so that they can update their implementation to accept their issuer string.

[panva]

The working group will work with this I-D as initial input for the updates

https://datatracker.ietf.org/doc/html/draft-jones-oauth-rfc7523bis-00

[panva]

Updated link to a WG document https://datatracker.ietf.org/doc/draft-ietf-oauth-rfc7523bis/