anchor.diff:  openssl rsa -pubout -in privkey.pem -out pubkey.pem
   ----
   
  +OpenSSL's command line utilities do not support Ed25519 keys yet.
  +See <<ed25519-generation,this section>> for Ed25519 key pair generation
  +example
  +
   === Involved RFC's?
   
  -* http://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32
  -* http://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-40
  -* http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-40
  -* http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-40
  +* https://tools.ietf.org/html/rfc7519
  +* https://tools.ietf.org/html/rfc7518
  +* https://tools.ietf.org/html/rfc7516
  +* https://tools.ietf.org/html/rfc7515
   * http://tools.ietf.org/html/draft-mcgrew-aead-aes-cbc-hmac-sha2-05
  -* http://tools.ietf.org/html/rfc3394
  -
  +* https://tools.ietf.org/html/rfc3394
  +* https://tools.ietf.org/html/rfc7517
  +* https://tools.ietf.org/html/rfc7638
  +* https://tools.ietf.org/html/rfc8037
   
   == Developers Guide
   
  
positive.code: it has less overhead. But if you are storing in the token claims that require
  privacy, JWE is the solution that should be used.
  
  
  [[generate-keypairs]]
  === How I can generate keypairs?
  
negative.code: |====================================================================================
  |Algorithm name     | Hash algorithms   | Keywords           | Priv/Pub Key?
  |Elliptic Curve DSA | sha256, sha512    | `:es256`, `:es512` | Yes
  |Edwards Curve DSA  | sha512            | `:eddsa`           | Yes
  |RSASSA PSS         | sha256, sha512    | `:ps256`, `:ps512` | Yes
  |RSASSA PKCS1 v1_5  | sha256, sha512    | `:rs256`, `:rs512` | Yes
  |HMAC               | sha256*, sha512   | `:hs256`, `:hs512` | No
  