anchor.diff:  
   When the `security-auth-token-enabled-components` property is set to 
   `all` or `management`,
  -you must provide credentials in the form of a valid bearer token
  -instead of a username and password. For example:
  +the cluster management service expects credentials in the form of a valid bearer token.
  +For example:
   
   ```
  -curl -H "Authorization: Bearer YWhhbWlsdG9uQGFwaWdlZS5jb206bXlwYXNzdzByZAo" http://example.com/management/regions
  +curl -H "Authorization: Bearer Y6bXlwYXNzdzByZAo" http://example.com/management/regions
   ```
   
   ## Java API
  
positive.code: 
  ## Cluster Management Configuration
  
  Locators started by gfsh will use the cluster management service REST API
  interface by default.
  The following properties control its functionality:
  
  - `http-service-port` needs to be be set to a non-zero value. If set to zero,
  there will not be an HTTP service available for the locator.
  The default value is 7070.
  
  - `enable-cluster-configuration` will need its default value of true.
  When set to false, the cluster management service REST API calls all return errors.
  
  - `enable-management-rest-service` will need its default value of true.
  The default value also start the JMX manager automatically.
  When set false, the cluster management REST service will not be started.
  
  By default, cluster management REST service logging occurs at the debug level.
  To increase logging to the info level,
  
negative.code: 
  Secure your cluster management service REST API
  by implementing the `SecurityManager` interface.
  When the interface is implemented,
  API requests require credentials.
  
  Credentials can take the form of a username/password pair or a valid bearer token.
  By default, the cluster management service expects credentials in the form of 
  a username and password, as in the example:
  
  ```
  