adds a JwtHelper.verifyJwt method in the style of this javascript method.
includes full test coverage of the verifyJwt method (for what that's worth :wink:)
passes ./gradlew test
uses the jjwt library that supports all 13 standard signature algorithms (depending on requirements the dependencies can be trimmed, see comments in build-extras.gradle).
The public API of the JwtHelper.verifyJwt method is decoupled from the underlying java JWT implementation (jjwt) with the exception of the Claims object returned from the method. I see three options:
decouple by making the method void (no return)
decouple by copying the Claims data structure into a new class (not completely trivial having inspected the Claims class)
leave it
Please advise a preference.
Ignore the whitespace changes in gradlew.bat, we can worry about that another time.
BTW I notice that the project doesn't import properly into Eclipse (though builds fine). All good, sorted, was an Eclipse metadata issue.
Before merging we'll have to make sure that these clerk-owned files are not touched by generation updates.
SPE-3699
For discussion purposes, not ready to merge
This PR
JwtHelper.verifyJwtmethod in the style of this javascript method.verifyJwtmethod (for what that's worth :wink:)./gradlew testbuild-extras.gradle).The public API of the
JwtHelper.verifyJwtmethod is decoupled from the underlying java JWT implementation (jjwt) with the exception of theClaimsobject returned from the method. I see three options:void(no return)Claimsdata structure into a new class (not completely trivial having inspected the Claims class)Please advise a preference.
Ignore the whitespace changes in
gradlew.bat, we can worry about that another time.BTW I notice that the project doesn't import properly into Eclipse (though builds fine).All good, sorted, was an Eclipse metadata issue.Before merging we'll have to make sure that these clerk-owned files are not touched by generation updates.