anchor.diff:  JSON Web Key (JWK) allows for a Public Key to be formatted in json and optionally Base64
   encoded.
   
  -At minimum `JWK` formatted Public Keys must contain the `kty` field.  RSA public keys must
  +At minimum JWK formatted Public Keys must contain the `kty` field.  RSA Public Keys must
   contain the `n` and `e` fields.
   
   The following example is the previously shown PKCS#8 PEM formatted Public Key converted to
  
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: 
  In the absence of a matching `kid`, all keys in the set will be tried in the order listed.
  
  The JWKS maybe supplied in plain JSON or Base64 URL encoded JSON format.
  
  ### Configuration Parameters
  
  