anchor.diff:  | Http Basic   | `buddy.auth.backends.httpbasic`
   | Session      | `buddy.auth.backends.session`
   | Token        | `buddy.auth.backends.token`
  -| SignedToken  | `buddy.auth.backends.token`
   | Jws Token    | `buddy.auth.backends.token`
   |================================================
   
  
positive.code: = buddy-auth - Auth facilities for ring based apps.
  Andrey Antukh, <niwi@niwi.be>
  0.3.0
  :toc: left
  :numbered:
  :source-highlighter: pygments
  
negative.code: If you are so inclined, you may use a different name for your token, using the **token-name** optional
  key when defining your backend.
  
  
  === Jws Token (Stateless)
  
  This backend is very similar to standard token backend previously explained, but instead
  of relying on _authfn_ for identify a token, it uses stateless tokens (contains all needed
  data in a token, without storing any information about the token in a database or elsewhere).
  
  This backend relies on the security of the high level signing framework for user authentication,
  concretely: JWS/JWT.
  
  Some valuable resources for learning about stateless authentication are:
  
  - http://lucumr.pocoo.org/2013/11/17/my-favorite-database/
  - http://www.niwi.be/2014/06/07/stateless-authentication-with-api-rest/
  
  
  == Authorization
  