anchor.diff:  
   == User Management APIs 
   
  -For a large entreprise solution, an LDAP or Okta integration is probably the most flexible, but it is also the most complex, and so for those that require the flexibility of an RBAC systems without the associated complexity, Kill Bill offers apis to manage the users/roles/permissions, where new user/roles/permissions will be stored in a database.
  +For a large entreprise solution, an LDAP or Okta/Auth0 integration is probably the most flexible, but it is also the most complex, and so for those that require the flexibility of an RBAC systems without the associated complexity, Kill Bill offers apis to manage the users/roles/permissions, where new user/roles/permissions will be stored in a database.
   
   This solution relies on a mixed solution between the `shiro.ini` file and the database backend: An initial user must be configured in the `shiro.ini` with at least enough permissions to use the User Management APIs:
   
  
positive.code: 
  Roles can be created by going to `/role_definitions/new`.
  
  ==== LDAP and Okta
  
  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.
  
  
negative.code: * Simple configuration file (`shiro.ini` file)
  * Database configuration
  * LDAP 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.
  
  