anchor.diff:  {"sub":"userid", "email":"user@example.com", ...}
   ----
   +
  -* A preferred user name using the `preferred_username` key. This is useful when the unique, unchangeable subject is a database key or UID, and a more human-readable name exists. This is used as a hint when provisioning the OpenShift user for the authenticated identity. For example:
  +* A preferred user name using the `preferred_username` key. This is useful when
  +the unique, unchangeable subject is a database key or UID, and a more
  +human-readable name exists. This is used as a hint when provisioning the
  +OpenShift user for the authenticated identity. For example:
   +
   ----
   {"sub":"014fbff9a07c", "preferred_username":"bob", ...}
   ----
   
  -.Master Configuration Using `*BasicAuthPasswordIdentityProvider*`
  +.Master Configuration Using *BasicAuthPasswordIdentityProvider*
   ====
   
   ----
  
positive.code: 
  As an administrator, you can configure OAuth using a
  link:master_node_configuration.html[master configuration file] to specify an
  link:#identity-providers[identity provider]. When running a master without a
  configuration file, the
  link:#AllowAllPasswordIdentityProvider[`*AllowAllPasswordIdentityProvider*`]
  identity provider is used by default, which allows any non-empty user name and
  password to log in. This is useful for testing purposes.
  
  To use other link:#identity-providers[identity providers], or to modify any
  link:#token-options[token], link:#grant-options[grant], or
  link:#session-options[session options], you must run the master from a
  configuration file.
  
negative.code: 
  To create the file, run:
  
  ----
  $ htpasswd -c </path/to/users.htpasswd> <user_name>
  ----
  
  To add or update a login to the file, run:
  
  ----
  $ htpasswd </path/to/users.htpasswd> <user_name>
  ----
  
  To remove a login from the file, run:
  
  ----
  $ htpasswd </path/to/users.htpasswd> -D <user_name>
  ----
  
  .Master Configuration Using *HTPasswdPasswordIdentityProvider*
  ====
  
  ----
  