Page Comparison

...

Please configure the FIXICC H2 according to the instance of the local.app.properties in your FIXICC H2 package, and set the following properties:

...

...

cuba.dbmsType = postgres
cuba.dataSourceProvider = application
cuba.dataSource.username = C##CUBA
cuba.dataSource.password =cuba
cuba.dataSource.dbName = PTGSDB 
cuba.dataSource.host = 10.68.21.182
cuba.dataSource.port = 1521
fixicch2.consul.encrypted_connection = true
fixicch2.consul.port = 8501
fixicch2.consul.insecure_connection_enabled = false
fixicch2.fixServerType = FIXEdge CPP

The following parameters can also be configured through the "Application Properties" page on FIXICC H2:

...

Default Value

...

Configures the type of server to work with.

Allowed values: FIXEdge CPP, FIXEdge Java, any other value means two types of supported servers.

...

CPP
fixicch2.prometheus.port = localhost
fixicch2.prometheus.port = 9090
fixicch2.prometheus.pollInterval = 5
fixicch2.metrics.support.fe = false
fixicch2.metrics.support.fej = true
fixicch2.unknownServer.autoRegistration = true

The following parameters can also be configurated through the "Application Properties" page on FIXICC H2:

...

1. Deploy the LDAP server

2. Set the following properties in the local.app.properties file:

   Name	Example value	Default value	Description
   ldap.contextSourceUrl	ldap://localhost:389	ldap://localhost:10389	Defines a URL for reaching the LDAP server
   ldap.contextSourceUserName	cn=admin,dc=epm-bfix,dc=local	uid=admin,ou=system	Indicates a username (principal) used for authentication. This is normally the distinguished name of the admin user.
   ldap.contextSourceBase	dc=epm-bfix,dc=local	dc=springframework,dc=org	Defines a base DN. If configured, all operations on contexts retrieved from ContextSource will be relative to this DN. By default, an empty name is set (i.e. all operations are related to the directory root).
   ldap.contextSourcePassword	ADMIN_PASSWORD	secret	Defines a password used for authentication. Login with default parameters for the first time. Then you can change the password in env docker-compose.
   ldap.referral	follow	follow	Defines the strategy to handle referrals, as described in this documentation
   ldap.sessionExpiringPeriodSec	120	30	Indicates a period in seconds after which the system terminates a user session if you deactivate the user or assign a new access group/matching rules to them
   ldap.userSynchronizationBatchSize	100	100	Defines the number of users that can be synchronized during the execution of the synchronizeUsersFromLdap() scheduled task
   ldap.userSynchronizationOnlyActiveProperty	true	true	If set to true, the synchronizeUsersFromLdap() scheduled task updates only the value of the Active attribute. Otherwise, the system updates all user details.
   ldap.cubaGroupForSynchronization	Company	Company	Defines access groups that are checked when the system executes the synchronizeUsersFromLdap() scheduled task.
   ldap.cubaGroupForSynchronizationInverse	false	false	If set to true, the system checks all groups when executing the synchronizeUsersFromLdap() scheduled task (except for the ones specified in ldap.cubaGroupForSynchronization)
   ldap.synchronizeCommonInfoFromLdap	true	true	If set to true, the synchronizeUsersFromLdap() scheduled task updates the values of the following user attributes in accordance with their state on the LDAP server side: Email, Name, First name, Last name, Middle name, Position, Language)
   cuba.web.standardAuthenticationUsers	admin, anonymous	admin, anonymous	Defines users that can log in to the system using standard CUBA credentials
   ldap.expiringSessionNotificationCron	*/10 * * * * *	*/10 * * * * *	Defines the cron expression for retrieving expired sessions from the middleware layer
   ldap.addonEnabled	true	false	If set to true, the LDAP add-on is enabled
   ldap.expiringSessionsEnable	true	true	If set to true, the system sends notifications to inform the user that their session is about to expire

3. If the group and user weren't set earlier you should create a posix group and a user in LDAP
4. Start the FIXICC H2
5. Select Administration > LDAP > LDAP Config in the menu on the left-side (items 1→2→3 in the figure below)
6. Check the connection by clicking Test Connection (item 4 in the figure below)
   Figure. The "Test Connection" button.
   
   
7. If the connection is successful, the FIXICC H2 will show the following message:
   
   Figure. The successful LDAP connection.
   
   
8. Go to the LDAP Matching Rules page by clicking LDAP Matching Rules 
9. Select the default rule in the table and click Edit or press Enter on your keyboard to edit the default rule
   Figure. The "LDAP Matching Rules" page.
   
   
10. Add the Role - system-full-access or your own role (in this case, the role's permissions must provide access to Allow all screens):
11. Click Add (see below):
    Figure. The "Add" button for adding the permissions.
    
    
    
    
12. Select the Role in the table (item 1 in the figure above)
13. Confirm your choice by clicking Select (item 2 in the figure above)
14. Logout by clicking the arrow at the bottom of the left-side menu (see below)
    
    Figure. The "Logout" button.
    
15. Login with the user's data whose role was added to the LDAP Matching Rules