anchor.diff:  [float]
   ==== 2.0.0
   
  -.new features
  +.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.
  +
  +.New Features
   * <<setting-up-field-and-document-level-security, Document and Field Level Security>> support has been added and can be
   configured per role.
   * Support for <<custom-realms, custom authentication realms>> has been added, allowing Shield to integrate with more authentication sources and methods.
   * <<submitting-requests-for-other-users, User impersonation support>> has also been added, which allows a user to send a request to elasticsearch that will be run
   with the specified user's permissions.
   
  -.bug fixes
  +.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.
   
  -.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
   
  -.bug fixes
  +.Bug Fixes
   * When using the <<ldap-user-search,LDAP user search>> mechanism, connection errors during startup no longer cause the node to stop.
   * The <<cache-eviction-api,Cache Eviction API>> no longer generates invalid JSON.
   * The <<audit-index,index output for auditing>> starts properly when forwarding the audit events to a remote cluster and uses
  
positive.code: of Shield will be added with a `.new` extension.
  
  [float]
  ==== updated role definitions
  The default role definitions in the `roles.yml` file may need to be changed to ensure proper functionality with other
  applications such as Marvel and Kibana. Any role changes will be found in `roles.yml.new` after upgrading to the new
  version of Shield. We recommend copying the changes listed below to your `roles.yml` file.
  
negative.code: [float]
  ==== 1.2.1
  
  .Bug Fixes
  * Several bug fixes including a fix to ensure that {ref}/disk.html[Disk-based Shard Allocation]
  works properly with Shield
  
  [float]
  ==== 1.2.0
  
  .Enhancements
  * Adds support for Elasticsearch 1.5
  
  [float]
  ==== 1.1.1
  
  .Bug Fixes
  * Several bug fixes including a fix to ensure that {ref}/disk.html[Disk-based Shard Allocation]
  works properly with Shield
  
  [float]
  ==== 1.1.0
  
  .New Features
  * LDAP:
  ** Add the ability to bind as a specific user for LDAP searches, which removes the need to specify `user_dn_templates`.
  This mode of operation also makes use of connection pooling for better performance. Please see <<ldap-user-search, ldap user search>>
  