anchor.diff:  `kty` field is missing or JSON text is found, but does not follow either JWK or JWKS
   format.
   
  -The JWK maybe supplied in plain JSON or Base64 encoded JSON format.
  +The JWK may be supplied in plain JSON or Base64 URL encoded JSON format.
   
   See https://tools.ietf.org/html/rfc7517[RFC-7517] for further details on JWK format and
   optional fields.
  
positive.code: -----END PUBLIC KEY-----
  ----
  
  MicroProfile JWT implementations must inspect supplied public key text for the `-----BEGIN
  PUBLIC KEY-----` header and parse the key as PCKS#8 if the header if found.
  
  Support for legacy PKCS#1 format is not required and should be considered vendor-specific.
  PKCS#1 formatted keys can be identified by the use of `-----BEGIN RSA PUBLIC KEY-----`
  header and footer.
  
  MicroProfile JWT implementations are required to throw a `DeploymentException` if given a
  
negative.code: java -jar movieservice.jar -Dmp.jwt.verify.publickey.location=orange.pem
  ----
  
  By convention of the MicroProfile JWT specification, property names are always lowercase
  and begin with `mp.jwt.`
  
  #### `mp.jwt.verify.publickey`
  
  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>>.
  
  The following example shows a Base 64 URL encoded JWK passed via system property.
  
  