Configure LPSM
You can configure system settings, monitor system performance, upload patches, backup and restore configurations, manage applications, and configure the Director setup settings from the System section.

You can also customize general settings, search related settings, date/time settings, notification settings and change the system password from the My Preferences section.

System Monitor
System Monitor contains widgets that display the system status.

You can view the status of different menu items such as Services, System Processes, Network Stack, Routing Table, ARP Table, Network Interfaces, and Disk Usage.

Services
Services lists all the service applications running in LPSM. You can view the status of each application and start, stop, or restart the services.
System Processes
System Processes shows all the processes running on the operating system where LPSM is installed. The process list shows information such as users, memory used by processes, commands on the run, and process IDs.
Network Stack
Network Stack shows information about the used network protocols and their corresponding network details.
Routing Table
Routing Table displays the routes to particular network destinations.
Address Resolution Protocol (ARP) Table
ARP Table displays a protocol for mapping an Internet Protocol address (IP address) to a physical machine address that is recognized in the local network. The item data lists the connection status for this protocol.
Network Interfaces
Network Interfaces displays the network status of LPSM. It also displays the status of all the active interfaces such as eth0, l0, he-ipv6, tun0, tun1, and tun10000.
Disk Usage
Disk Usage displays the total disk space used by the LPSM file systems. It also displays the available disk, disk usage, and location of the file system.
System Monitoring via SNMP
You can use SNMPv2 or SNMPv3 to monitor the status of the LPSM system components and services using their respective OIDs.
LPSM uses the base OID 1.3.6.1.4.1.54322.4 to get a list of the exposed OIDs and their corresponding information. You can also use the OID of the individual system components and services in LPSM to get their status.
Syntax for snmpwalk via SNMPv2:
Syntax for snmpwalk via SNMPv3:
System Settings
System Settings allows you to configure all system related settings for LPSM. It enables you to configure general settings, SMTP settings, NTP settings, SNMP settings, HTTPS settings, support connection settings and allows you to set the SSH Key Pair for li-admin.

Each setting needs to be saved separately before moving on to the next setting.
Applications
You can upload application packages and import Plugins in LogPoint Search Master from the Applications page. An application package is a collection of pluggable components such as Authentication and System Notification. LPSM provides the LPSM_Default package by default.

Plugins
Enables connection to external data and systems so you can add specific features and functionality to your Logpoint platform. Termed ”Plugins” in the Logpoint UI, they are a synonymous with Authentication, Process Commands, Collectors, Fetchers and Enrichment integrations.
Currently, there are three out-of-the-box authentication integrations for Director LPSM:
LDAP Authentication

You can request new features from Logpoint Customer Service. When the feature is developed, the .pak file of the new integration is uploaded in Integrations of the Logpoint Service desk. You can then download the latest version of the integration and import the .pak file from Settings >> System >> Applications in LPSM.
To install, import the .pak file. After installation it is listed in INSTALLED PLUGINS in Settings >> System >> Plugins.
LDAP Authentication
LDAP (Lightweight Directory Access Protocol) integration in LPSM offers User Authentication, User Management, Role-Based Access Control, and Centralized Data Management.
You can use LDAP for LPSM login authentication and configure it to pull user authentication and role-based access control rules from your LDAP directory. LPSM users are already defined in LDAP so you don’t need to recreate them.
By default, LDAP Authentication is automatically installed in LPSM and cannot be deleted. Configure the LDAP Strategy in LPSM to use LDAP. LDAP strategy is the rules and configurations for deploying and maintaining LDAP services for your organization. LDAP strategy can vary depending on what your needs and objectives are.
LDAP Concatenation of Users and Permission Groups
The LDAP user “LDAP User 1” belongs to LDAP Groups “LDAPG-1” and “LDAPG-2” in the LDAP directory.
There are two Permission Groups PG1 (with Read Site Permission only) and PG2 (with Read, Create, and Delete Site Permissions) created in Logpoint.
PG1 is mapped to User Group UG1, and PG2 is mapped to UG2.
UG1 has the Object Permission of Device-1 and Repo-1, and UG2 has the Object Permission of Device-2 and Repo-2.
If you map the LDAPG-1 to UG1 and LDAPG-2 to UG2, the LDAP User 1 has the concatenated Site and Object Permissions of UG1 and UG2. In this case, the Site Permission is Read, Create, and Delete and the Object Permission is of Device-1, Repo-1, Device-2, and Repo-2.
You can now use LDAP Authentication to log in to LPSM.

Strategy-User group Mapping - UI
LDAP server data is connected with LPSM and stored in the database. First, the connection is made with the LDAP server using data from the LDAP strategy. Once the connection is established, the data (LDAP group) from the server is obtained. After the LDAP groups are obtained, they are listed in the User Group Mapping. Here, the user must select the required LDAP group to map to the LPSM user group. Once the mapping is established, the content: LDAP group, user group, and the DN associated with it are stored in the database. Any update to user group mapping is reflected every time the user logs in to Logpoint.
Supported Login formats (LDAP)
The following three parameters can be used to log in via LDAP.
Using DN:
Using sAMAccountName:
Using uid:
Communication
The parameters used for communication are:
Host
Port
Bind DN
Bind DN password
SSL enabled or not
There are two ways to communicate:
Simple communication
Communication using SSL
For simple communication, the Python-LDAP library is used. The host and the 389 port are used to connect to the LDAP server. Once the connection is established, Bind DN and Bind Password are used to bind to the required user.
For SSL communication, the first step is to set the certificate for the SSL connection. After the certificate is set, the process is similar to simple communication. Here, the port used is 636.
My Preferences
Click the User drop-down on the top-right corner of the interface and select My Preferences.

Last updated
Was this helpful?





























