Crane Truck

V1.5.0
JAAS Configuration

JAAS content:
The content of the JAAS file. You can directly set it here, or give the location of the JAAS file
JAAS file:    The JAAS-STANDARD file
Authentication key:    in the JAAS file, you may have multiple key. By default, key should be Authentication-1 or BonitaAuthentication-1 (depend of the Bonita Version)
Try to log using the JAAS configuration
Verify the JAAS configuration by logging with a user / password
Login:    The login name
Password:      The password to check the JAAS configuration
LDAP Step by step     If your JaasContent reference a LDAP source (com.sun.security.auth.module.LdapLoginModule), then a step by step connection is perform, to understand which step failed

{{cranectrl.jaas.inprogress}}

{{cranectrl.jaas.status.detailsjsonmap.status}}

{{cranectrl.jaas.status.detailsjsonmap.error}}

{{cranectrl.jaas.status.detailsjsonmap.error}}

Ldap Connection step by step
{{detail}}
How to configure the JAAS file ? Show
First, create a JAAS file with the content.
Second: change the service
Third, give the JAAS file: In the studio : open the BonitaBPMSubscription.ini file and add -Dtomcat.extra.params=-Dcom.java.security....

In the Tomcat:

JAAS Detail operation Specify each component of the JAAS file, and then this tool will play step by step each operation the com.sun.security.auth.module.LdapLoginModule play

Url (userProvider): The attribute urlProvider of the LdapLoginModule. Connection to the LDAP database, and the root hierarchy
user Filter (userFilter): The attribute userFilter of the LdapLoginModule. How the user can be found in the hierarchy ?
Identity (authIdentity): The attribute authIdentity of the LdapLoginModule. May be empty
Use SSL (useSSL): SSL protocol should be used ?
Login: To verify the different parameters, a login is run
Password:  

{{cranectrl.ldaploginmodule.inprogress}}

{{cranectrl.ldaploginmodule.status.connection}}

{{cranectrl.ldaploginmodule.status.error}}

 Details:
JAAS Environment Use this JAAS file:

Leave this input empty to retrieve the Environement Variable java.security.auth.login.config


{{cranectrl.jaasenvironment.status.info}}

{{cranectrl.jaasenvironment.status.error}}

Jaas File : {{cranectrl.jaasenvironment.status.variable}}

Jaas Content :

LDAP Synchronizer
Path LdapSynchronizer configuration:
Tenant Id:
{{cranectrl.status.properties.status}}

{{cranectrl.status.properties.error}}

{{cranectrl.alltests.status}}

{{cranectrl.alltests.error}}

LDAP Connection
properties files ldap.properties

Host Connection to your LDAP directory. Contains the host and the port
Authentication Type Different way to connect the LDAP directory. Use 'simple'
Principal DN In a LDAP directory, you connect with a user/password. This is the user name, as a LDAP form
Password The password of the LDAP user
Directory user type use 'person' for LDAP, 'user' for ActiveDirectory
Paged When your directory is big (more than 1000 entries), it's better to synchronize page per page
Size of page The size of one page
Run a simple search
Verify the search activity by running a simple search in the directory
SearchDN Give a hierarchy where the search starts
SearchFilter Give a filter base on attributes

{{cranectrl.statusldap.inprogress}}

{{cranectrl.statusldap.detailsjsonmap.connection}}

{{cranectrl.statusldap.detailsjsonmap.search}}

{{cranectrl.statusldap.detailsjsonmap.error}}

uid sn cn givenName record
{{oneresult.uid}} {{oneresult.sn}} {{oneresult.cn}} {{oneresult.givenName}} {{oneresult}}
Bonita Connection
properties files bonita.properties

BonitaHome The path to the Bonita Home
Domain (tenant) The Domain, equals to the TenantId
login Technical user of the tenant (install)
password The password of the user
technicalUser The technical user of the platform (platformAdmin)
technicalPassword The password of the technical user of the platform

{{cranectrl.statusbonita.inprogress}}

{{cranectrl.statusbonita.info}}

{{cranectrl.statusbonita.error}}

Logger
properties files sync.properties

Log dir path
Log file date prefixe (example yyyy-MM-dd)
log level
Synchronize
properties files sync.properties

Watch directory

Name Search DN Search filter
 {{onedir.name}}
  

Users

Error level:
User name case of the Bonita imported users
Bonita users who should not be synchronized (user names separated by commas)
Specifies whether the tool should deactivate Bonita users which are not present in LDAP
Specify the role that will be affected to Bonita users

Groups

Allow recursive
Group by hierarchy
Name Group_DN Forced group name
 {{onedir.name}}
  
Group by Search
Name Search DN Search Filter
 {{onedir.name}}
  

Tests


{{cranectrl.synctest.inprogress}}

{{cranectrl.synctest.status}}

{{cranectrl.synctest.error}}

Watch Directory test

Test Nb record Status
{{oneresult.name}} {{oneresult.size}} Error: {{oneresult.error}} One Record {{oneresult.example.user_name}}
Mapper
properties files mapper.properties

Bonita attribut Ldap attributes Example
{{oneitem.b}} {{oneitem.e}}
{{cranectrl.mappertest.status}}

{{cranectrl.mappertest.error}}

Users Management
Max user to display
Filter on user Name

{{cranectrl.listusers.status.inprogressgetuser}}

User Name First Name LastName State
{{oneitem.username}} {{oneitem.firstname}} {{oneitem.lastname}} {{oneitem.enable}}
Total of users {{cranectrl.listusers.totalusers}} Nota: the operation is not apply to myself (if you click on Delete, you don't delete yourself for example)

{{cranectrl.listusers.status.info}}

{{cranectrl.listusers.status.error}}