anchor.diff:  }
   ```
   
  -### The `Claims` Enumeration Utility Class
  +### The `Claims` Enumeration Utility Class, and the Set of Claim Value Types
   
   The `org.eclipse.microprofile.jwt.Claims` utility class encapsulate an enumeration
   of all the standard JWT related claims along with a description and the required
  
positive.code:     @Inject // <5>
      @Claim("custom-missing")
      private ClaimValue<Optional<Long>> custom;
  ----
  <1> Injection of the raw MP-JWT token string.
  <2> Injection of the jti token id as an `Optional<String>` wapper.
  <3> Injection of the aud audience claim as a Set<String>. This is the required
  
negative.code: claim name using the Claims.iat enum value.
  <5> Injection of a custom claim that does exist will result in an Optional<Long>
  value for which isPresent() will return false.
  <6> Another inection of a non-proxyable raw type like java.lang.Long, but the use of the javax.inject.Provider interface
  allows for injection to occur in non-RequestScoped contexts.
  <7> Injection of a JsonArray of role names via a custom "roles" claim.
  
  The example shows that one may specify the name of the claim using a
  string or a `Claims` enum value. The string form would allow for specifying non-standard
  claims while the `Claims` enum approach guards against typos and mis-spellings.
  
  #### Handling of Non-RequestScoped Injection of Non-Proxyable Claim Values
  MP-JWT implementations are required to validate the use of claim value injection into contexts that do not match
  @RequestScoped. When the target context has @ApplicationScoped or @SessionScoped scope, implementations are
  required to generate a `javax.enterprise.inject.spi.DeploymentException`. For any other context, implementations
  should issue a warning, that may be suppressed by an implementation specific configuration setting.
  
  [NOTE]
  If one needs to inject a claim value into a scope with a lifetime greater than @RequestScoped, such as
  @ApplicationScoped or @SessionScoped, one can use the javax.inject.Provider interface to do so.
  
  ### JAX-RS Container API Integration
  The behavior of the following JAX-RS security related methods is required for
  