This repository has been archived by the owner on Mar 3, 2022. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #635
JsonService
now has an optionaljwtHandler
parameter.application/jwt
is added to valid content types. When receiving a valid response with content typeapplication/jwt
, thejwtHandler
will be invoked rather than simply parsing the response body as JSON.UserInfoService
now creates aJsonService
using a customjwtHandler
. The handler code is copied fromResponseValidator
with minor adaptions.JoseUtil.validateJwt
now has an optionaltimeInsentive
parameter which defaults to false. If this value is true, the claimsiat
,nbf
andexp
will not be validated.userInfoJwtIssuer?: 'ANY' | 'OP' | string;
ANY
means the issuer claim is ignoredOP
means the issues claim must match the OP's issuer identifier URLstring
allows for a custom specified issuer