anchor.diff:  while an example of the latter is:
   https://github.com/MicroProfileJWT/wfswarm-jwt-auth-tck
   
  -Additionally, you must provide an implementation of the `org.eclipse.microprofile.jwt.tck.util.ITokenParser`
  -interface using the `java.util.ServiceLoader` pattern. This is used by the TCK tests that validate the
  -basic behavior of the MP-JWT JsonWebToken implementation independent of any container runtime deployment. An
  -example of an `ITokenParser` implementation can be found in:
  -https://github.com/MicroProfileJWT/wfswarm-jwt-auth-tck/tree/master/src/main/java/org/eclipse/microprofile/jwt/wfswarm/tck[TCKTokenParser.java].
  -
   
   == Creating Your Implementation TCK Harness Artifact
   As described, you need to create an artifact that bundles a LoadableExtension
  
positive.code: </project>
  ----
  <1> org.eclipse.microprofile.jwt:microprofile-jwt-auth-tck is the MP-JWT artifact
  that contains the base `LoadableExtension` and `ApplicationArchiveProcessor` classes,
  as well as the `ITokenParser` harness factory interface and `TokenUtils` class.
  <2> org.eclipse.microprofile.jwt:microprofile-jwt-auth-tck type=test-jar is the MP-JWT
  TCK tests themselves you need to run for the TCK. You would only need this if you are
  running the TCK from within your TCK harness project.
  
negative.code: == Running Your Implementation With the TCK
  Once you have built and installed your TCK harness artifact, you can run the
  TCK tests against it by using either the `tokens-se` or `container` profiles.
  
  === container Profile
  The container profile is a test of JAX-RS client tests that validate a JAX-RS endpoint bundled in a WebArchive deployment
  