anchor.diff:  === Adding a Public Key
   
   The https://tools.ietf.org/html/rfc7519[JWT specification] defines various levels of security of JWTs that one can use.
  -The {mp-jwt} specification requires that its JWTs utility signed tokens that use RSA-256 as the signature algorithm. This in
  +The {mp-jwt} specification requires that JWTs that are signed with the RSA-256 signature algorithm. This in
   turn requires a RSA public key pair. On the REST endpoint server side, you need to configure the location of the RSA public
   key to use to verify the JWT sent along with requests. The `mp.jwt.verify.publickey.location=publicKey.pem` setting configured
   previously expects that the public key is available on the classpath as `publicKey.pem`. To accomplish this, copy the following
  
positive.code: |quarkus.jwt.realm-name|Quarkus-JWT|Name to use for security realm.
  |quarkus.jwt.auth-mechanism|MP-JWT|Name to use for authentication mechanism
  |mp.jwt.verify.publickey|none|The `mp.jwt.verify.publickey` config property allows the Public Key text itself to be supplied as a string.  The Public Key will be parsed from the supplied string in the order defined in section <<Supported Public Key Formats>>.
  |mp.jwt.verify.publickey.location|none|onfig property allows for an external or internal location of Public Key to be specified.  The value may be a relative path or a URL.
  |mp.jwt.verify.issuer|none|config property specifies for the expected value of the `iss`
                             claim of the JWT to be specified. This match is required for JWT validation.
  |===
  
  === Supported Public Key Formats
  
negative.code: 
  == Explore the Solution
  
  The solution repository located in the `using-jwt-rbac` {quickstarts-archive-url}[directory] contains all of the versions we have
  worked through in this quickstart guide as well as some additional endpoints that illustrate subresources with injection
  of `JsonWebToken`s and its claims into those using the CDI APIs. We suggest that you check out the quickstart solutions and
  explore the `using-jwt-rbac` directory to learn more about the {extension-name} extension features.
  