anchor.diff:  
   Secure your cluster management service REST API
   by implementing the `SecurityManager` interface.
  -With the interface implemented,
  -API requests will require credentials.
  -By default, those credentials will need to be in the form of 
  +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:
   
   ```
  
positive.code: 
  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:
  
  ```
  curl -H "Authorization: Bearer YWhhbWlsdG9uQGFwaWdlZS5jb206bXlwYXNzdzByZAo" http://example.com/management/regions
  ```
  
  ## Java API
  
negative.code: 
  ## Cluster Management Configuration
  
  Locators started by gfsh support the cluster management service REST API.
  
  Three property settings must be in effect to enable the cluster management REST API. These are in effect, by default, for gfsh-initiated locators.
  
  - `http-service-port` must be set to a non-zero value. If set to zero,
  no HTTP service is available for the locator. The default HTTP service port is 7070.
  
  - `enable-cluster-configuration` must be set to true.
  When set to false, all of the cluster management service REST API calls return errors.
  
  - `enable-management-rest-service` must be set to true.
  When set to false, the cluster management REST service does not start.
  
  By default, cluster management REST service logging occurs at the debug level.
  To increase logging to the info level,
  