Authentication Logs

Overview

The Mideye Server’s Authentication Logs provide a comprehensive and detailed view of user authentication attempts handled by the RADIUS server. This interface allows administrators and support teams to monitor, analyze, and respond to authentication events from various sources effectively. Authentication logs can be filtered, inspected for detailed contextual data, and used to perform administrative actions, such as blocking users or IP addresses (upcoming feature).

Table View

Columns

The main Authentication Logs page displays a table containing the following key columns:

• Time:
  Displays the timestamp of the authentication attempt in UTC format.

• Username:
  Shows the name of the user who attempted to authenticate. This may include users from an internal database or Active Directory.

• RADIUS Client:
  Indicates the client system or application from which the authentication request originated.

• MSISDN:
  Displays the Mobile Subscriber Integrated Services Digital Network Number (MSISDN) or Token Number of the user, if applicable.

• Authentication Type:
  Specifies the method of authentication used during the attempt. Common examples include MOBILE and TOUCH_MOBILE.

• Result:
  Displays the outcome of the authentication attempt. Possible values are:

• Successful: The user authenticated successfully.
• Failed: The authentication attempt was unsuccessful.

Detailed View

Viewing Detailed Information

Clicking on any log entry in the table will open a detailed view on the right side of the interface. This detailed view offers additional insights and contextual data for the selected authentication attempt, including:

• Time of Attempt:
  The exact timestamp when the authentication attempt occurred.

• MSISDN:
  Detailed MSISDN information if provided.

• RADIUS Client and Mideye Server:
  Shows which RADIUS client sent the request and the Mideye Server handling the request.

• Authentication Type and Result:
  Detailed description of the authentication method used (e.g., PASSWORD, TOUCH_MOBILE) and the outcome (Successful or Failed).

• Country Code and Called Station ID:
  Displays geographical and network information related to the request when available. (Upcoming feature)

• Authentication Context:
  Provides metadata such as:

• Calling Station ID: The IP address or host of the incoming request. (Upcoming feature)
• User Type: Classification of the user (e.g., DIRECTORY_USER).
• Token Number and Other Session Data: Relevant data for session management and troubleshooting.

Additional User Information (if applicable)

• LDAP Profile:
  Displays details such as LDAP server name, Distinguished Name (DN), and related directory information.

• Active Directory Response:
  Indicates if there was a response from Active Directory, along with relevant details.

• Switch Response Info:
  Provides additional data specific to the Mideye session.

Filtering Options

To facilitate effective log management, the interface includes a filtering section where administrators can apply filters based on various parameters, such as:

• Date Range:
  Select the start and end dates for log filtering.

• Username:
  Filter logs by specific user(s).

• Authentication Types:
  Narrow down logs based on authentication methods.

• RADIUS Clients:
  Focus on logs from specific RADIUS clients.

• Results:
  Filter based on authentication outcomes (e.g., Successful, Failed).

Administrative Actions

Blocking Feature (Upcoming)

In future releases, administrators will have the ability to block users or IP addresses directly from the detailed view. This feature is intended to enhance security response by allowing immediate blocking actions for potentially malicious or unauthorized authentication attempts.

Example Scenarios

• Troubleshooting Failed Authentications:
  Use the detailed view to understand why a specific authentication attempt failed by inspecting related data, such as the Calling Station ID, Authentication Type, and any associated messages.

• Filtering for Specific Users:
  Utilize the filtering options to monitor and analyze authentication activity for a particular user or group of users.

• Troubleshooting Phone Number:
  If a user is expecting to get SMS OTP and the MSISDN field for that user says N/A. The Phone number is either incorrectly inserted in to the user repository. (Active Directory or Mideye Database) Or it does not exist. So please update the phone number and let the user try again.

• Troubleshooting Phone Number:
  If a user is expecting to receive an SMS OTP but the MSISDN field for that user displays N/A, the phone number may be incorrectly entered in the user repository (Active Directory or Mideye Database) or it might be missing entirely. To resolve this issue:

Note

Ensuring that the MSISDN field is accurately populated is crucial for the successful delivery of SMS OTPs.

---