anchor.diff:  java -jar movieservice.jar -Dmp.jwt.verify.publickey.location=file:///opt/keys/orange.pem
   ----
   
  -Parsing of the file contents occurs as defined in "Supported Public Key Formats"
  +Parsing of the file contents occurs as defined in <<Supported Public Key Formats>>
   
   ##### http: URL Scheme
   
   HTTP and HTTPS URL paths allow for the Public Key to be fetched from a remote host, which
   may be the JWT Issuer or some other trusted internet or intranet location.
   
  -The location supplied must respond to an HTTP GET.  Parsing of the http message body
  -occurs as defined in "Supported Public Key Formats"
  +The location supplied must respond to an HTTP GET.  Parsing of the HTTP message body
  +occurs as defined in <<Supported Public Key Formats>>
   
   [source,bash]
   ----
  
positive.code:  - JSON Web Key (JWK) Base64 URL encoded
   - JSON Web Key Set (JWKS) Base64 URL encoded
  
  Attempts to parse the Public Key material will proceed in the order specified above until
  a valid Public Key can be derived.
  
  Support for other Public Key formats such as PKCS#1, SSH2, or OpenSSH Public Key format is
  
negative.code: default format for OpenSSL, many public/private key tools and is natively supported in
  Java.
  
  The format consists of a Base64 URL encoded value wrapped in a standard `-----BEGIN PUBLIC
  KEY-----` header and footer.  The Base64 URL encoded data can be decoded and the resulting
  byte array passed directly to `java.security.spec.PKCS8EncodedKeySpec`.
  
  The following is an example of a valid RSA 2048 bit Public Key in PKCS#8 PEM format.
  