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 Jan 20, 2025. It is now read-only.
It seems that Identity Server optionally sets the typ header-property to at+jwt which seems to be allowed according to RFC 9068? Currently the parseJwt returns null if the typ property is defined and not set to jwt. Would there be a downside removing this constrain?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It seems that Identity Server optionally sets the
typ
header-property toat+jwt
which seems to be allowed according to RFC 9068? Currently the parseJwt returns null if thetyp
property is defined and not set tojwt
. Would there be a downside removing this constrain?The text was updated successfully, but these errors were encountered: