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.
This PR continues with making the builder API as compact as possible, introduces the shortcuts to optimize some flows.
In the flow where the claims are built from the empty builder,
Jwt.claims()
transition is now optional, every time I seeJwt.claims().claim("a", "b")
I think this is suboptimal.So, instead of
Jwt.claims().issuer("issuer").subject("sub").sign()
one can just doJwt.issuer("issuer").subject("sub").sign()
.Creates
sign()
,encrypt
andinnerSignAndEncrypt
shortcuts to optimize the flows where the keys are configured and where the default RSA algorithms are used:Jwt.claims("/token.json").sign()
is equivalent toJwt.sign("/token.json")
(same for the maps and jsonobject)
Jwt.claims("/token.json").jwe().encrypt()
is equivalent toJwt.encrypt("/token.json")
(same for the maps and jsonobject)
Jwt.claims("/token.json").innerSign().encrypt()
is equivalent toJwt.innerSignAndEncrypt("/token.json")
(same for the maps and jsonobject)
Instant
overloads for theiss
andexp
claims