- changed status to resolved
Support for dpop_bound_access_tokens in client metadata
Issue #467
resolved
Do you plan to support dpop_bound_access_tokens
in registration metadata as specified in https://datatracker.ietf.org/doc/html/rfc9449#name-client-registration-metadat ?
Obviously I can also use ClientMetadata.setCustomField("dpop_bound_access_tokens", true)
and corresponding getter. But I’m wondering will that approach be compatible with the future versions of the Nimbus library if you add new variable with setter/getter methods for that flag?
Comments (2)
-
-
New release:
version 11.11 (2024-05-15) * Adds support for the dpop_bound_access_tokens OAuth 2.0 client metadata parameter. * Updates to Nimbus JOSE+JWT 9.39.1
- Log in to comment
Apparently we forgot this :)
Commit: 3fb28d196b6c6832a7983bc9b8e84ac05486eaf9