You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
The existing support cannot be configured to validate the JWT audience or issuer fields.
IIUC the default behaviour for pyjwt when decoding a JWT which includes an audience claim is to raise an error if that audience claim isn't validated. The end result is - our JWT support doesn't work for JWT's which include an audience claim today.
I'd like us to enhance our JWT processing to support:
configurable iterable of audiences (audiences are strings; I ask for the ability to supply a set of these at configuration time because pyjwt supports it, not because I know of anybody who needs us to validate on multiple audiences)
configurable issuer (issuer is also a string)
If these values are set in configuration we should include them in the call to jwt.decode.
The existing support cannot be configured to validate the JWT
audience
orissuer
fields.IIUC the default behaviour for pyjwt when decoding a JWT which includes an audience claim is to raise an error if that audience claim isn't validated. The end result is - our JWT support doesn't work for JWT's which include an audience claim today.
I'd like us to enhance our JWT processing to support:
If these values are set in configuration we should include them in the call to jwt.decode.
audiences
andissuer
should be optional.How the configuration might look when we're done:
The text was updated successfully, but these errors were encountered: