anchor.diff:  ----
   
   ==== POST JSON Data
  -Alternatively, the user can `POST` his or her credentials to the `/api/v1/auth/login` end point in order to retrieve a token.
  -The JSON object must contain these fields:
  -
  -* `username` The username of the user
  -* `password` The password of the user
  -
  -If the authentication was successful, the server will respond with a JSON object containing a single property:
  -
  -* `token` The token to be sent on every subsequent request.
  +Alternatively, the user can ```POST``` his or her credentials to the ```/api/v1/auth/login``` end point in order to retrieve a token.
  +The JSON object must contain the following fields:
  +
  +* ```username```: The username of the user
  +* ```password```: The password of the user
  +
  +If authentication has been successful, the server will respond with a JSON object containing a single property:
  +
  +* ```token```: The token to be sent on every subsequent request.
   
   Additionally, the token will also be provided in a cookie.
   
  
positive.code: * Authentication via API token
  * No authentication - Access via anonymous user
  
  WARNING: Sending user credentials as base64 encoded string, or as plaintext is highly insecure to be used on an open network. This method MUST not be used in scenarios other than debugging and development when the connection between server and client is trusted.
  
  ==== Authentication Configuration
  
  Gentics Mesh uses JWT (JSON Web Token) to handle authentication. It is thus required to create a cryptograph key to sign the sign and verify the generated JWT's. 
  Typically, if no keystore file has been provided, Gentics Mesh will create one on the basis of the configuration details in `mesh.yml`. If the `keystorePassword` property is omitted, a password will be generated randomly and stored in the configuration file.
  
  It can be configured within the `mesh.yml` configuration file. 
  
  [source,bash]
  ----
  
negative.code:   -H 'Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VyVXVpZCI6IjNjYjY2YzU0MmFlMzRiMDFiNjZjNTQyYWUzY2IwMWRiIiwiaWF0IjoxNDkxNzY1NDEzLCJleHAiOjE0OTE3NjkwMTN9.UY8OgjiK5qyZobAWt6X1Vd1Z-zg68BeJgGZKbW4Ucj0=' \
  ----
  
  It is possible to manually revoke a previously issued token via ```DELETE /api/v1/users/:userUuid/token```. Once the token is invalidated it can no longer be used for authentication.
  
  === Anonymous Access 
  
  Gentics Mesh first and foremost keeps your content safe - all data including media assets such as images, videos, and documents are secured and need authentication to be retrieved. However, sometimes it may be desirable to serve public content with Gentics Mesh. 
  
  That is why Gentics Mesh instances ship with an included ```anonymous``` user/role/group set. 
  If no authentication details are provided Gentics Mesh will automatically try to authenticate with the user ```anonymous```.
  
  You can assign ```readPublished``` permissions to the ```anonymous``` role for all elements you want to be publicly available.
  
  NOTE: Assigning further permissions would of course allow for other operations to be granted. 
  
  Anonymous access can be configured in the ```mesh.yml``` configuration file:
  
  [source,yaml]
  ----
  