anchor.diff:  
   TIP: If a configuration management tool is used, the properties file can be created and is used as startup configuration
   
  +NOTE: If credentials are provided preemptive auth is used for all defined ElasticSearch nodes.
  +
   .Configuration properties for access to ElasticSearch
   [source]
   ----
   elasticUrl=http://elastic:9200
   elasticIndexStrategy=daily
  -elasticUser=elastic
  -elasticPassword=changeme
  +elasticGlobalUser=elastic
  +elasticGlobalPassword=changeme
   ----
  +
  +====== Configure ElasticSearch Credentials
  +
  +It is possible to define credentials for each ElasticSearch node individually.
  +Credentials for each node must be stored in `${OPENNMS_HOME}/etc/org.opennms.features.flows.persistence.elastic.credentials.cfg`.
  +The format is as follows:
  +
  +```
  +[<scheme>]<host>:<port>=<username>:<password>
  +```
  +
  +.Custom credentials
  +```
  +localhost:9200 = ulf:ulf
  +10.10.0.1:9200 = ulf:flu
  +```
   
   ===== Configure NetFlow v5 Listener on a Minion
   
  
positive.code: | optional
  | `daily`
  
  | _elasticUser_
  | User name in when link:https://www.elastic.co/guide/en/x-pack/current/setting-up-authentication.html[X-Pack Security] is configured
  | optional
  | -
  
  | _elasticPassword_
  | Password in when _X-Pack Security_ is configured
  | optional
  | -
  
  
negative.code: 
  [options="header, autowidth"]
  |===
  | Property | Description | Required | default
  
  | _elasticUrl_
  | URL(s) to ElasticSearch nodes. Can either point directly to ReST API or seed nodes. The format is: `<host>:<port>`. Comma separate multiple values.
  | required
  | `http://localhost:9200`
  
  