anchor.diff:  ----
   
   
  -WARNING: Take care that using jws for create tokens, the data is serialized using
  -json + base64 and signed using strong cryptography signatures. That method ensure
  -that the data can not be manipulated by third party but it not protect it from
  -privacy. If you need store private data in the token, consider using JWE.
  +WARNING: Take care that using jws for create tokens, the data is serialized
  +using json + base64 and signed using strong cryptography signatures. That method
  +ensure that the data can not be manipulated by third party but it not protect it
  +from privacy. If you need store private data in the token, consider using JWE.
   
   
   ==== JWE Token
   
  -This authentication backend consists in using self contained tokens for authenticate
  -the user. It works identically to the JWS (explained previously) with the exception
  -that instead of only signing data, it also encrypts the data, so ensuring the data
  -privacy.
  +This authentication backend consists in using self contained tokens for
  +authenticate the user. It works identically to the JWS (explained previously)
  +with the exception that instead of only signing data, it also encrypts the data,
  +so ensuring the data privacy.
   
   You can create the backend instance so:
   
  
positive.code: 
  The possible values for the `:policy` key are: `:deny` and `:sameorigin`.
  
  WARNING: The frame-ancestors directive from the CSP Level 2 specification officially
  replaces this non-standard header.
  
  
  ==== Strict Transport Security
  
  This is a security related chain handler that adds the `Strict-Transport-Security`
  header to the response.
  
  HTTP Strict Transport Security (often abbreviated as HSTS) is a security feature
  that lets a web site tell browsers that it should only be communicated with using
  HTTPS, instead of using HTTP.
  
  Usage example:
  
  
negative.code: (session/session {:storage (my-storage-constructor)})
  ----
  
  If you want implement own session storage, take a look to the `:inmemory`
  builtin one.
  
  
  === Authentication
  