anchor.diff:  
   Parsing of the file contents occurs as defined in <<Supported Public Key Formats>>
   
  -##### file: URL Scheme
  +##### `file:` URL Scheme
   
   File URL paths supplied as the location allow for explicit externalization of the
   file via full url.
  
positive.code: must verify the `iss` claim of incoming JWTs is present and matches the configured value
  of `mp.jwt.verify.issuer`.
  
  If the `mp.jwt.verify.issuer` config property has not been set, any issuer is allowed.
  
  NOTE: In most cases relying on the digital signature check via the Public Key alone is
  sufficient to establish trust.
negative.code: 
  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.
  