Skip to content

Authentication Logs – Monitor RADIUS Login Attempts and Results

The Authentication Logs page provides a comprehensive, real-time view of all RADIUS authentication events processed by MideyeServer. Every login attempt — whether successful, failed, or timed out — is recorded with detailed metadata including the username, calling station ID, authentication type, RADIUS client, and fraud score.

Use this page to investigate authentication issues, verify that multi-factor authentication (MFA) is functioning correctly, identify suspicious login patterns, and create static filter rules to block malicious actors. The authentication log is an essential tool for security monitoring, compliance auditing, and troubleshooting user access problems in your RADIUS infrastructure.

Authentication logs support advanced filtering by date range, username, calling station ID, authentication type, authentication result, and RADIUS client — enabling rapid identification of specific events across large volumes of authentication data.

Required Role: ROOT, SUPER_ADMIN, ADMIN, or OPERATOR

Navigation: Home → Logs → Authentication Logs

RoleView LogsView DetailsCreate Filter Rules
ROOT
SUPER_ADMIN
ADMIN
OPERATOR

The main data grid displays authentication events in a paginated, sortable table. By default, logs are sorted by time in descending order (newest first) and the page loads with today’s date range pre-selected.

Default visible columns:

ColumnDescription
TimeTimestamp of the authentication event (always visible)
UsernameThe user identity that attempted authentication
MSISDNMobile phone number associated with the user
Authentication TypeMethod used for authentication (SMS, Mobile App, Token, etc.)
Fraud ScoreIP reputation score from Mideye Shield (displays ”–” if unavailable)
ResultColor-coded outcome: green (Successful), red (Failed), yellow (Timed Out)

Hidden by default (can be enabled via column visibility settings):

ColumnDescription
RADIUS ClientThe NAS or network device that initiated the authentication request
Calling Station IDThe originating IP address or MAC address of the end user

Click the Filter icon in the toolbar to open the filter panel. All text-based filters use debounced input (1-second delay) to reduce unnecessary server requests.

FilterTypeDescription
Start DateDate pickerBeginning of the time range (defaults to today at midnight)
End DateDate pickerEnd of the time range (defaults to end of today)
UsernameText inputSearch by username (partial match)
Calling Station IDText inputSearch by originating IP or MAC address
Authentication TypesMulti-selectFilter by one or more authentication methods
RADIUS ClientsMulti-selectFilter by one or more RADIUS client names (dynamically populated)
Authentication ResultsMulti-selectFilter by outcome: Successful, Failed, Timed Out

Available Authentication Types:

  • PASSWORD — Password-only (1FA) authentication
  • MOBILE — SMS OTP delivery
  • TOKEN — Hardware or software token
  • CONCAT — Password concatenated with OTP
  • PLUS — Mideye Plus (push notification)
  • TOUCH — Touch-based approval
  • TOUCH_PLUS — Touch with Plus activation
  • TOUCH_MOBILE — Touch with mobile fallback
  • ASSISTED_LOGIN — Approver-assisted login
  • SHARED_ACCOUNT — Shared account authentication
  • ON_PREM — On-premises hardware token (OATH)
  • PASSWORD_RESET — Password reset flow
  • MAGIC_LINK — Magic link authentication

Click Apply to execute the filter, or Reset to clear all filter fields.

Click any row in the data grid to open the detail drawer on the right side of the screen. The drawer displays:

  • Time — Event timestamp
  • Username — Authenticated user identity
  • MSISDN — Mobile phone number
  • Calling Station ID — Originating address (if available)
  • Country Code — Geographic origin (or “N/A” if unavailable)
  • Called Station ID — Target address (if available)
  • Authentication Type — Method used
  • RADIUS Client — NAS device name
  • Result — Authentication outcome
  • Mideye Server — Processing server instance
  • Info — Additional context (if available)

Below the summary, the Details section renders the full authentication event trace as an expandable tree structure. Node entries can be expanded to reveal nested key-value pairs with translated labels.

Creating Static Filter Rules from Failed Attempts

Section titled “Creating Static Filter Rules from Failed Attempts”

When viewing a failed authentication event, the detail drawer displays Block buttons next to the Username and Calling Station ID fields. Clicking a Block button opens a dialog to create a new static filter rule that blocks future authentication attempts matching that value.

Create Static Filter Rule Dialog:

FieldTypeValidationDescription
CommentTextMax 255 charactersOptional note explaining why the rule was created

The rule is created with action BLOCK and operator EQUAL_TO. If an identical rule already exists, an informational message is displayed instead.

Field NameTypeDescription
timeDateTimeTimestamp when the authentication event occurred
usernameStringUser identity used in the authentication attempt
msisdnStringMobile phone number of the user
callingStationIdStringOriginating IP address or MAC address of the client device
authTypeEnumAuthentication method used (PASSWORD, MOBILE, TOKEN, etc.)
fraudScoreIntegerIP reputation score from Mideye Shield (null if unavailable)
resultEnumAuthentication outcome: SUCCESSFUL, FAILED, TIMED_OUT
radiusClientStringName of the RADIUS client (NAS) that sent the request
countryCodeStringTwo-letter country code of the originating IP
calledStationIdStringTarget network address
mideyeServerStringServer instance that processed the request
infoStringAdditional context or error information

Purpose: Reload the authentication log data from the server. Steps: Click the refresh (loop) icon in the toolbar. Result: The data grid reloads with the latest events matching the current filter criteria.

Purpose: Narrow down displayed authentication events by specific criteria. Steps:

  1. Click the filter icon in the toolbar.
  2. Set desired filter values (date range, username, etc.).
  3. Click Apply.

Result: The data grid updates to show only events matching all specified filter criteria.

Purpose: Create a static filter rule to block future authentication attempts from a specific username or IP address. Prerequisites: The authentication event must have a FAILED result. Steps:

  1. Click a failed authentication row to open the detail drawer.
  2. Click the Block button next to the Username or Calling Station ID.
  3. Optionally enter a comment (max 255 characters).
  4. Click Block to create the rule.

Result: A new static filter rule is created with action BLOCK and operator EQUAL_TO for the selected attribute and value.

  1. Open the filter panel and set the date range to the relevant time period.
  2. Enter the username in the Username filter.
  3. Select “Failed” in the Authentication Results filter.
  4. Click Apply.
  5. Click on a failed event to view the full authentication trace in the detail drawer.
  6. Examine the Details tree to identify the root cause (invalid password, expired token, locked account, etc.).
  1. Filter by Authentication Result: “Failed”.
  2. Sort by time (descending) to see the latest failures.
  3. Look for patterns: repeated failures from the same Calling Station ID or against the same username.
  4. Review the Fraud Score column for high-risk IP addresses.
  5. Use the Block action on suspicious entries to create filter rules.
  1. Filter by a specific Authentication Type (e.g., PLUS, TOUCH, or MOBILE).
  2. Verify that authentication events of the expected type appear for the target users.
  3. Check that results show “Successful” for properly configured users.
IssuePossible CauseResolution
No logs appearDate range too narrowExpand the date range or reset filters
Missing RADIUS client in filterClient recently createdRefresh the page to reload the client list
Fraud score shows ”–“Mideye Shield disabled or IP not scoredVerify Mideye Shield is enabled and configured
Block button not visibleEvent is not a failed attemptBlock is only available for FAILED results
Block button not visibleInsufficient permissionsBlock requires ADMIN role or higher