5.1 Setting Up Core Engine

The Core Engine of ACDI consists of the following components:

NOTE:Any changes made to the core engine setup will be implemented after restart.

5.1.1 LDAP Connections

Using this component, you can add and configure LDAP connections between the ACDI server and Data connectors. When you create a new data connector using Data Connection Wizard, the LDAP connection is automatically added to the connection list.

On the homepage, go to Administration > Core Engine > LDAP Connections to see the available LDAP connections.

You can perform the following operations on the LDAP connections:

Add an LDAP Connection

NOTE:It is recommended to add new connections using Connection Wizard.

  1. Click the + icon and provide the following details:

    • Name of connection

    • Type (Data connector used)

    • URL

    • Username

    • Password

    • (Optional) Connection Timeout

  2. Click the save icon.

Edit an LDAP Connection

  1. Click the connection you want to edit and modify the following values:

    • Name of connection

    • Type (Data connector used)

  2. Click Auth to enable authentication.

  3. Click the LDAP Server list and edit the following:

    • URL

    • Username

    • Password

    • Connection Timeout

  4. Click the TLS options list and edit the following:

    • Private key

    • Certificate

    • CA

  5. Click save icon.

5.1.2 LDAP Authentication Settings

This component consists of all parameters and attributes required for authentication operation.

Table 5-1 LDAP Authentication Settings Parameters

Parameters

Description

Search Scope

Specify the portion of the directory tree that a user can search within. ACDI supports three different scopes:

  • base

  • one

  • sub

Base DN

Helps to search users from the base container by multiple options such as through user’s ACDI and user’s data.

NOTE:Only users located in the specified containers according to Search Scope will be able to login.

Membership attribute

Defines user roles, permissions, and linkage attribute between the user and the object that will have entitlements can be defined.

By default, entitlements are granted with groupMembership attribute.

Right mapping attribute

Attribute in object (by default it is Group) which holds ACDI entitlement info. By default it is Description. It is recommended to change it to custom auxiliary attribute.

Filter group names with regular expressions

Specifies the groups that you must look up to determine entitlements.

Additional LDAP filter

To use a custom attribute for role assignments.

Authentication timeout

Set timeout for authentication in seconds. The minimum timeout is 5 seconds.

Search attributes

Helps to search users. For example: mail, cn

Additional attribute

Saves additional information from LDAP.

Perform the following steps to configure LDAP authentication:

  1. On the Homepage go to Administration > Core Engine > LDAP authentication settings.

  2. Modify all the parameters and attributes according to the requirements. For more details about parameters check

  3. Click the save icon.

  4. Log in to Identity Console and create the required users and a group for entitlement configuration.

    For more information, see Creating a User section and Creating a group section.

    NOTE:You must add one value in the description. For example, add an empty JSON string {} as the description.

  5. Add the users to the group created.

  6. Go to ACDI to assign entitlements and access the group you created.

  7. Click manage user accounts icon in the top right corner.

  8. Specify a username and click Get User Data. Password is optional.

  9. Edit the user’s attributes as per your requirements.

  10. In ACDI Filtered Groups for User, select appropriate group and assign ACDI roles, add Report and Dashboard filters (support regex) and click the Save icon.

    NOTE:Raw field will display final value of Right mapping attribute. If you see Bug icon near your Group, enter {} in a Raw field.

5.1.3 Web Server Settings

ACDI provides the following web server settings for troubleshooting events:

  • External Hostname

  • External Port Number

  • Local Hostname

  • Local Port Number

  • Path to keystore file of external host

  • Keystore password of external host

  • Path to keystore file of local host

  • Keystore password of local host

Using the Self Test Settings parameters, you can monitor the health of ACDI and see the results on Administration > Health and Metrics > System Health.

Using Opensearch Stats Settings parameters, you can monitor the Opensearch status of ACDI and see the results on Administration > Health and Metrics > Opensearch Health.

Bypass bodyPraser URL

5.1.4 Mailer Settings

Using Mailer Settings, you can configure an email ID. The Reporting service uses this email ID to send scheduled reports and in-system notifications.

5.1.5 Scheduled Tasks

You can perform multiple tasks and schedule them to run automatically by providing proper scripts and arguments.

To schedule a task, perform the following steps:

  1. On the Homepage go to Administration > Core Engine > Scheduled tasks.

  2. Expand a task and specify the required details.

  3. (Optional) To add multiple tasks, click the plus + icon to add a new task.

  4. Click save icon.

5.1.6 Session Settings

You can configure the following settings for a web server session:

Settings

Description

Cookies name

The name of the cookie used.

Secret word

The value used for encrypting your session ID.

Session max age

The maximum duration for which a session remains active.

Session stored LDAP attributes

Stores some LDAP attributes of current users in the session.

5.1.7 Web Proxies List

You can configure the list of endpoints and ports used for redirecting requests of a proxy. Also, you can add custom headers to a proxy.

5.1.8 WS Proxies List

Perform the following steps to add a WS proxy to the list:

  1. On the Home page, go to Administration > Core Engine > W S Proxies list.

  2. Click the plus + icon.

  3. Provide the required details.

  4. Click the save icon.

5.1.9 Local Access List

Here, you can check the list of local users who can access ACDI. You can also add a new local user account and update the following details:

  • Proxies allowed for user

  • Roles apply to user

  • AuditProxy API’s allowed

5.1.10 List of Rule Presents

This component contains the list of rules used for advanced role customizations. You can configure a data transformation of ACDI proxy in the calls for appropriate users. Additionally, you can specify endpoints for the rules and URLs. These endpoints will be used when a rule runs your JavaScript code and modifies data.

5.1.11 AuditProxy API List

Use this component for advanced role configuration consisting of a list of APIs and their configuration details.

5.1.12 Role List

Here, you can see a list of roles that can authenticate to the ACDI setup. You can add or edit a list of allowed rules and a list of allowed APIs for each role.

5.1.13 Post Configuration of Core Engine

Perform the following steps after making any change in the Core Engine configuration to reflect the changes:

NOTE:Any changes made to the core engine setup will be implemented after restart.

  1. After saving the changes, click control service icon.

  2. Click Restart.

  3. Refresh the page and log in again.