anchor.diff:  
   [source,clojure]
   ----
  -(require '[buddy.auth.backends.httpbasic :refer [http-basic-backend]])
  +(require '[buddy.auth.backends :as backends])
   (require '[buddy.auth.middleware :refer [wrap-authentication wrap-authorization]])
   
   ;; Simple self defined handler for unauthorized requests.
  
positive.code: (def app (-> your-ring-app
               (wrap-authentication backend)))
  ----
  
  
  The corresponding login endpoint should have a similar aspect to this:
  
  
negative.code: The `authfn` should return something that will be associated to the `:identity`
  key in the request.
  
  The responsability of _buddy_ is just parse request and call the user function
  authenticate it. The token building and storage is a user responsability.
  
  You can see a complete example of using this backend <<example-token,here>>.
  
  
  ==== JWS Token
  
  Is a backend that uses signed and self contained tokens to authenticate the user.
  
  It behaves very similarly to the _Token_ backend (previously explained) with the
  difference that this one does not need additional user defined logic to validate
  tokens, because as we previously said, everything is self contained.
  
  This type of token mechanism enables a complete stateless authentication because the
  server does not need to store the token and related information, the token will
  