anchor.diff:  ./bin/kibana
   ----
   
  -. Log in to {kib} as the `elastic` user.
  +. Log in to {kib} as the `elastic` user. Use this superuser account to 
  +{kibana-ref}/tutorial-secure-access-to-kibana.html[manage spaces, create new users, and assign roles]. If you're running {kib} locally, go to `http://localhost:5601` to view the login page.
   
   [[minimal-security-whatsnext]]
   ==== What's next?
   
   Congratulations! You enabled password protection for your local cluster to
   prevent unauthorized access. You can log in to {kib} securely as the `elastic`
  -user. If you're running a <<single-node-discovery,single-node cluster>>, then
  -you can stop here.
  +user and create additional users and roles. If you're running a <<single-node-discovery,single-node cluster>>, then you can stop here.
   
   If your cluster has multiple nodes, then you must configure Transport Layer
   Security (TLS) between nodes. <<dev-vs-prod-mode,Production mode>> clusters
  
positive.code: NOTE: You only need to set passwords for the `elastic` and `kibana_system` users
  when enabling minimal or basic security.
  
  . Start Elasticsearch. For example, if you installed Elasticsearch with a
  `.tar.gz` package, run the following command from the Elasticsearch directory:
  +
  [source,shell]
  
negative.code: When the {es} security features are enabled, users must log in to {kib} with a
  valid username and password.
  
  You'll configure {kib} to use the built-in `kibana_system` user and the password that
  you created earlier. {kib} performs some background tasks that require use of the
  `kibana_system` user.
  
  This account is not meant for individual users and does not have permission to log in
  to {kib} from a browser. Instead, you'll log in to {kib} as the `elastic` superuser. 
  
  . Add the `elasticsearch.username` setting to the `KIB_PATH_CONF/kibana.yml`
  file and set the value to the `kibana_system` user:
  