anchor.diff:  * Simple configuration file (`shiro.ini` file)
   * Database configuration
   * LDAP integration
  -* Okta integration
  +* Okta/Auth0 integration
   
   For simple deployments where only few static users/roles need to be assigned, the `shiro.ini` file is the simplest and the best option. By default both Kill Bill (`shiro.ini`) and Kaui ship with an `admin` user (and its password `password`) that has all the permissions. One can immediatly log-in to Kaui using such user, and start configuring tenants as needed.
   
  
positive.code: 
  == LDAP configuration
  
  To enable LDAP, Kill Bill needs to be launched with the following System Properties (note that the values here are just examples and might need to be updated depending on your LDAP configuration):
  
  [source,properties]
  ----
  killbill.server.ldap=true
  org.killbill.security.ldap.dnSearchTemplate=uid={0},ou=users,dc=mycompany,dc=com
  org.killbill.security.ldap.searchBase=ou=groups,dc=mycompany,dc=com
  org.killbill.security.ldap.groupSearchFilter=memberOf=uid={0},ou=users,dc=mycompany,dc=com
  
negative.code: 
  Roles can be created by going to `/role_definitions/new`.
  
  ==== LDAP, Okta, and Auth0
  
  If you are delegating roles and users management to a third-party system, Kaui only needs to know the login of the users. Password and roles being managed outside of Kill Bill, you need to access your third-party system to set and update these.
  
  