anchor.diff:  //
  -// Copyright (c) 2016-2017 Eclipse Microprofile Contributors:
  +// Copyright (c) 2016-2018 Eclipse Microprofile Contributors:
   // Red Hat, IBM, Tomitribe
   //
   // Licensed under the Apache License, Version 2.0 (the "License");
  
positive.code: is required in each JWK and incoming JWT being authenticated.
  
  MicroProfile JWT implementations are required to throw a `DeploymentException` if a JWKS
  is supplied via static configiuration and contains multiple keys, but no `kid`.
  
  MicroProfile JWT implementations are required to return a 401 at runtime in situations
  where a `kid` is either required or does not match.
  
negative.code: ### Obtaining the Public Key
  
  In practice, the Public Key is often obtained manually from the JWT Issuer and stored in
  or passed to the binary of the Microservice.  If your public Keys do not rotate frequently, then storing them in the binary image or on disk is a realistic option for many environments.
  For reference, SSL/TLS Certificates to support HTTPS, which are also Public Key based, are
  usually configured in the JVM itself and last for up to two years.
  
  