Now that we have all the pieces in place for JWT, we can now register the JWT validator as our validator of choice:
The validator will inspect the incoming requests for valid JWT authorization headers. It will verify their expiration, their required claims, and the user it represents. Once done, it goes in the same rule/annotation security flow that cbsecurity leverages.
Each module can also override its validator via its configuration setting
cbsecurity.validator. So if the global validator is something other than JWT but your module REQUIRES JWT validation, then add it in your
The JWT validator will discover the incoming JWT token from 3 sources:
authorizationheader using the bearer token approach
- 2.Custom header configured in your settings:
rcvariable with the same name as
If your rules have the
permissionselement or your
secureannotations have context, then we will treat those as the scopes/permissions to check the user/token must have at validation.
The validator will have the following validation process:
- Verify the JWT exists via the
authorizationheader or custom header
rc[ 'x-auth-token' ]
- Verify we can decode it
- Verify if it has not expired from the token itself
- Verify it has the required claims
- If token storage is enabled, verify the token in the permanent storage
- Verify the subject (
sub) claim and try to retrieve the user it represents
- Try to authenticate the user for the request
- Verify the subject has the right permissions or that the token has the right scopes attached to it.
- If all is valid, then place the token in
prc.jwt_tokenand the payload in
- If all is valid, then place the user object in
prc.oCurrentUseror the variable of your choice via the
- Continue or block
That's it! You can create your rules and annotations just like you used to, but now the validator will ensure valid JWT tokens are passed for those requests.