anchor.diff:  with the specified user's permissions.
   
   .bug fixes
  +* <<configuring-auditing, Auditing>> now captures requests from nodes using a different system key as tampered requests.
  +* The <<audit-index, index output for auditing>> stores the type of request when available.
   * `esusers` and `syskeygen` work when spaces are in the elasticsearch installation path.
   * Fixed a rare issue where authentication fails even when the username and password are correct.
   
  -[float]
  -==== 2.0.0-beta1
  -
  -This release is primarily for compatibility with Elasticsearch 2.0.0-beta1.
  +.breaking changes
  +* All files that Shield uses must be kept in the <<ref-shield-files-location, configuration directory>> due to the enhanced security of Elasticsearch 2.0.
  +* The network format has been changed from all previous versions of Shield and a full cluster restart is required to upgrade to Shield 2.0.
   
   [float]
   ==== 1.3.2
  
positive.code: [float]
  ==== 2.0.0
  
  .breaking changes
  * All files that Shield uses must be kept in the <<ref-shield-files-location, configuration directory>> due to the enhanced security of Elasticsearch 2.0.
  * The network format has been changed from all previous versions of Shield and a full cluster restart is required to upgrade to Shield 2.0.
  
  [float]
  ==== 2.0.0-rc1
  
  .enhancements
  * Added a caching interface that can be used by <<custom-realms, custom authentication realms>> to integrate with the <<cache-eviction-api, cache eviction api>>.
  
  .bug fixes
  * <<configuring-auditing, Auditing>> now captures requests from nodes using a different system key as tampered requests.
  * The <<audit-index, index output for auditing>> stores the type of request when available.
  * <<ip-filtering, IP filtering>> could have allowed a user to block all access to their node if the system was incorrectly configured, but now explicitly
  allows connections from all addresses that the node is bound to so that connections coming from the node's host will not be blocked.
  
  [float]
  ==== 2.0.0-beta2
  
  .new features
  * <<setting-up-field-and-document-level-security, Document and Field Level Security>> support has been added and can be
  configured per role.
  
negative.code: === Upgrading Shield
  
  To upgrade Shield, just uninstall the current Shield plugin and install the new version of Shield. Your configuration
  will be preserved and you do this with a rolling upgrade of Elasticsearch when upgrading to a new minor version; a full
  cluster restart is required when upgrading from Elasticsearch 1.x. On each node, after you have stopped it run:
  
  [source,shell]
  ---------------------------------------------------
  