Configuring One Identity Safeguard for Privileged Sessions (SPS) to use external indexers
The following describes how to configure One Identity Safeguard for Privileged Sessions (SPS) to accept connections from external indexer services.
To configure SPS to accept connections from external indexer services
-
Log in to the SPS web interface, and navigate to Basic Settings > Local Services > Indexer service.
-
Select Indexer service.
-
Select Enable remote indexing.
Figure 260: Basic Settings > Local Services > Indexer service > Enable remote indexing — Configure external indexers
-
In the Listening addresses > Address field, select the network interface where SPS should accept external indexer connections. Repeat this step to add other interfaces if needed.
The available addresses correspond to the interface addresses configured in Basic Settings > Network > Interfaces. Only IPv4 addresses can be selected.
-
Select Restrict clients, and list the IP address and netmask of your external indexer hosts.
Use an IPv4 address.
-
Click Commit.
Installing the external indexer
Prerequisites
The external indexer can be installed on the following 64-bit operating systems: Red Hat Enterprise Linux Server 7, 8, and their derivatives such, as CentOS, Oracle Linux, AlmaLinux, Rocky Linux, etc.
NOTE: Derivatives are supported only if an issue can be reproduced on an official RHEL distribution. Do not report issues specific to a derivative OS but not to RHEL.
To install the external indexer
-
Log in as root to the host that you want to use to index your audit trails.
-
Copy the installer package to the host.
NOTE: Due to legal reasons, installation packages of the external indexer application will be available only from the SPS web interface. After SPS versions 6.4 and 6.0.3 are released, the installation packages will be removed from our website.
-
Install the package using the package manager of the operating system. For example:
yum install external-indexer-standalone-<version-number>.x86_64.rpm
The installer performs the following steps automatically.
-
Unpacks the indexer files into the /opt/external-indexer/ directory.
-
Installs the related init scripts (the /etc/init.d/external-indexer init script, and adds the init script configuration to /etc/sysconfig/external-indexer).
-
Creates the indexer user and usergroup. This is an unprivileged user that is used to run the indexer application.
-
Registers the service to start automatically on system boot. Note that the indexer init script uses bind mount points.
-
Configure the indexer. For details, see Configuring the external indexer.
Configuring the external indexer
To connect to One Identity Safeguard for Privileged Sessions (SPS) and index the audit trails, you must configure the external indexer.
|
|
Caution:
Unless you know exactly what you are doing, modify only the parameters you are instructed to. |
To configure the external indexer
-
Appendix: Log in to the SPS web interface, and navigate to Basic Settings > Local Services > Indexer service.
-
To export the configuration file for the external indexer, click Export.
NOTE: The Export button is displayed only after the configuration that enables SPS to use remote indexers is committed.
The configuration file contains the listening address (IP and port) of SPS and the necessary keys for SSL authentication.
Upload the file to the external indexer host.
-
On the external indexer host, import the configuration file with the following command:
indexer-box-config <configuration-file>.config
-
To configure the external indexer service, open the /etc/indexer/indexerworker.cfg configuration file for editing.
-
To edit the number of worker groups assigned to a certain worker process type, find the worker_groups line.
A worker group has the following parameters:
-
name: the name of the worker group
-
count: the number of workers to use for processing
-
capabilities: the types of jobs the process performs (index, screenshot, video, near-realtime)
NOTE: Setting the near-realtime capability exclusively determines whether active or closed sessions are indexed. For example:
-
If you set [near-realtime, index] capabilities for a worker, that worker only indexes active and ongoing sessions.
-
If you set [index, screenshot, video] capabilities for a worker, that worker only indexes closed sessions.
NOTE: If you configure a connection policy with near real-time priority (Connection policy > Enable indexing > Priority), you must configure indexer workers that are capable of near real-time indexing. To configure such indexer workers, set the near-realtime capability for the relevant workers.
NOTE: Indexer workers with the near-realtime capability require fewer CPU cores but more memory than indexer workers that do not have this capability.
Make sure that the sum value of the workers are equal to the number of CPU cores in the host (or the number of CPU cores minus one if you want to save resources for other tasks).
One Identity recommends using dedicated hosts for external indexing. If the host is not dedicated exclusively to the external indexer, decrease the number of workers accordingly.
-
(Optional) To fine-tune performance, you can configure the number of OCR threads each worker can initiate using the ocr_thread_count key.
The default setting is 3. When configuring this setting, pay attention to the available CPU cores, as raising the number of possible threads too high can impact performance negatively.
-
(Optional) If instructed by One Identity Support, configure the OCR engine.
Find the engine key, and change its value to one of the following options:
-
omnipage-external is the default setting. It provides the best performance and stability by allowing workers to initiate multiple OCR threads.
This setting also allows you to search for images where OCR could not be performed. On the search UI of SPS, enter the OOCCRRCCRRAASSHH search string to list all such images. If possible, contact our Support Team, to help One Identity to further improve the engine.
NOTE: Multiple OCR threads can only speed up processing graphical protocols (RDP, VNC, and ICA trails), and do not affect the processing speed for terminal-based protocols (telnet and SSH).
-
omnipage only supports one OCR thread per worker.
If you have to use this option, make sure to also set the ocr_thread_count to 0.
-
Save your changes.
-
(Optional) Continue with uploading decryption keys to index encrypted audit trails. For more information, see Uploading decryption keys to the external indexer.
-
(Optional) Start the indexer service. For more information, see Starting the external indexer.
Uploading decryption keys to the external indexer
If the audit trails you want to index are encrypted, complete the following steps to make the decryption keys available for the indexer.
To make the decryption keys available for the external indexer
-
Obtain the RSA private key and copy it to the external indexer's host.
-
Use the indexer-keys-json utility to transform the private key to the required JSON format. When executed, the script asks for the path to the private key, and the password of the private key. After the conversion, the password is removed.
The utility automatically adds the private key to the /etc/indexer/indexer-keys.cfg keystore file. If you want to use a different keystore file, use the --keystore argument to specify another file. If the keystore already includes the private key you want to add, it will be ignored.
-
In the /opt/external-indexer/usr/bin/ folder, issue the following command: indexer-keys-json
-
Provide the absolute path to the private key. Alternatively, you can include this information as a parameter: indexer-keys-json --private-key <path-to-private-key>
-
If the key is password protected, enter the password to the private key.
-
To add additional keys, re-run the indexer-keys-json command.
-
You can now start the indexer service. For more information, see Starting the external indexer.
