You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This must match the serverside `mp.jwt.verify.issuer` for the token to be accepted as valid.
383
-
<2> The `upn` claim is defined by the {mp-jwt} spec as the preferred claim to use for the `Principal` seen by the container security APIs.
384
-
<3> The `group` claimprovides the groups and top-level roles associated with the JWT bearer.
385
-
<4> The `birthday` claim.
386
-
It can be considered a sensitive claim, so consider encrypting the claims, as described in xref:security-jwt-build.adoc[Generate JWT tokens with SmallRye JWT].
385
+
<1> Sets the `iss` (issuer) claim in the JWT.
386
+
This value must match the server-side `mp.jwt.verify.issuer` configuration for the token to be considered valid.
387
+
<2> Specifies the `upn` (User Principal Name) claim, which the {mp-jwt} specification defines as the preferred claim for identifying the `Principal` in container security APIs.
388
+
<3> Defines the `groups` claim, which provides the group memberships and top-level roles assigned to the JWT bearer.
389
+
<4> Adds a `birthdate` claim.
390
+
Because this can be considered sensitive information, consider encrypting claims as described in xref:security-jwt-build.adoc[Generate JWT tokens with SmallRye JWT].
387
391
388
392
Note that for this code to work, you need the content of the RSA private key corresponding to the public key you have in the `TokenSecuredResource` application.
389
393
Take the following PEM content and place it into `security-jwt-quickstart/src/test/resources/privateKey.pem`:
0 commit comments