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: org.killbill.security.ldap.permissionsByGroup=support-group: entitlement:*\nfinance-group: invoice:*, payment:*\nops-group: *:*
  ----
  
  Notes:
  
  * If no groups are defined in LDAP, all users will only have read-only permissions
  * Before an LDAP user can use Kaui, an admin needs to associate his login to the right tenants (see below)
  * If you have trouble connecting to your LDAP system, enable DEBUG logging off the package `org.apache.shiro` in your `logback.xml` and check the logs
  
  == KAUI
  
  
negative.code: 
  == Summary
  
  1. User, roles, permissions need to be configured on the server side (`shiro.ini`, database, LDAP, Okta/Auth0, ...)
  2. Tenants can then be created (using a user whole role's permissions allow such operation)
  3. Mapping between tenant and allowed users need to be defined in Kaui
  