eG Login Details Test

Administrators monitor login details to maintain the security, efficiency, and proper usage of the eG manager. This helps detect unauthorized access or unusual login patterns, identify inactive or unused accounts that may pose security risks, and understand how users interact with the manager whether through web or CLI. Monitoring login activity also supports compliance auditing, informed resource and license allocation, and faster troubleshooting of login-related issues. For this purpose, administrators can use the eG Login Details test to gain detailed visibility into user login behavior.

This test tracks and reports user login activity on the eG manager to help administrators monitor usage patterns, identify inactive accounts, and detect potential security issues. This test reports the number of non-default users, indicating custom or additional user accounts created on the manager. This test also captures the number of logins in the last 24 hours, providing insight into recent user activity, and highlights users who have not logged in during the last 30 days, which can be useful for identifying inactive or idle accounts. In the process, the test also distinguishes between web logins and CLI (command-line interface) logins, helping to analyze how users are accessing the environment.

Target of the test : eG Manager

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for the eG manager that is being monitored.

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed .

Host

The host for which the test is to be configured.

Port

The port number at which the specified host listens.

Timeout

Specify the duration (in seconds) for which this test should wait for a response from the eG manager. If there is no response from the eG manager beyond the configured duration, the test will timeout. By default, this is set to 240 seconds.

ExecutionTime

Specify when the test should run. Administrators can choose to execute the test either Daily or Hourly, and define the exact time of execution using Hours and Minutes. This helps administrators to control the frequency and timing of the test to match monitoring requirements or reduce overhead.

JMX Remote Port

Here, specify the port at which the JMX listens for requests from remote hosts. In the <EG_MANAGER_INSTALL_DIR>\manager directory (on Windows; on Unix, this will be the /opt/egurkha/manager directory) of the eG manager, you will find a management.properties file. Set the port defined against the com.sun.management.jmxremote.port parameter of the file as the JMX Remote Port.

JNDI Name

The JNDIName is a lookup name for connecting to the JMX connector. By default, this is jmxrmi. If you have registered the JMX connector in the RMI registry using a different lookup name, then you can change this default value to reflect the same.

JMX User, JMX Password, and Confirm Password

By default, JMX requires no authentication or security. Therefore, the User, Password , and Confirm Password parameters are set to none by default.

JMX Bind Address

JMX Bind Address denotes the IP address or hostname on which the Java Management Extensions (JMX) service will listen for incoming remote management connections. By default, this flag is set to Local Host indicating that the JMX service binds to the default IP address (127.0.0.1) of the target host. However, if the JMX service is listening on different IP address of the target host, then set this flag to Other IP.

Provider

This test uses a JMX Provider to access the MBean attributes of the eG manager and collect metrics. Specify the package name of this JMX Provider here. By default, this is set to com.sun.jmx.remote.protocol.

DD Frequency

Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Non-default users

Indicates the number of non-default users logged into the eG manager, excluding built-in or pre-defined users.

Number

 

Logins in last 24 hrs

Indicates the total number of successful user logins to the eG manager in the last 24 hours.

Number

 

Users who have not logged in during last 30 days

Indicates the number of users who have not logged into the eG manager in the past 30 days.

Number

 

Web logins

Indicates the number of users who accessed the eG manager through the web interface.

Number

 

CLI logins

Indicates the number of users who accessed the eG manager through the CLI.

Number