MP JWT 2.1 specification outlines how signed JSON Web Token (JWT) tokens issued by OpenId Connect (OIDC), OAuth2 and other trusted providers can be verified and their claims used for Role Based Access Control (RBAC) of microservice endpoints. It also supports inner-signed and encrypted JWT tokens.
The Spec team meets on Thursdays every other day. The joining details can be found in the MicroProfile calendar.
Add a plug-in to import the Spec blogs. Make sure the Spec category exists on Blogs, etc (iterate on what blogs do in the Compatible page with importing content)
Functional changes
- Support for RSA-OAEP-256 key management algorithm for decrypting JWT tokens has been added
- ‘mp.jwt.decrypt.key.algorithm’ property for listing multiple JWT decryption algorithms has been added, requiring that both ‘RSA-OAEP’ and ‘RSA-OAEP-256’ must be accepted if ‘mp.jwt.decryption.algorithm’ is not set
- ‘mp.jwt.verify.token.age’ property for restricting a token age has been introduced
- ‘mp.jwt.verify.clock.skew’ property for configuring a leeway for the token expiry and age verification has been introduced