Last update:
Track a user login journey
Aug 21, 2026
Scenario
A user contacts support stating that they were unable to sign in to an application and are unsure what went wrong. An administrator needs to review the user’s login activity to understand what happened during the sign-in attempt, identify where the authentication flow stopped, and determine whether the issue was related to the password, multi-factor authentication (MFA), one-time password (OTP), authenticator, passkey, or the application itself. This investigation is performed using audit visibility only, without making any configuration changes.Prerequisites
- Admin has access to the Activities tab based on role permissions.
- A user identifier (for example, username or email address) and an approximate date and time of the reported sign-in issue.
Roles authorized
Steps
- Sign in to Aikyam Identity Console.
- Navigate to Users from the left navigation pane.
- Search for the user using Basic search or Advanced search and open the user profile.
- Go to the Activities tab to view the User activity events recorded for the user.
- Review events around the reported timeframe and, if needed, adjust visible columns to improve visibility of authentication activity.
- Review the events in sequence to understand the authentication flow, including the authentication methods used (password, multi‑factor authentication (MFA), one‑time password (OTP), or passkey) and where the sign‑in process completed or stopped.
- Check the Application ID in the events to confirm the application involved and determine the outcome of the login attempt.
Note:
- Audit logs reflect system-recorded activity only and do not capture user intent or external factors such as network or browser behavior.
- If no authentication events are found for the expected timeframe, the sign-in attempt may not have reached AIC.
Previous:
Export logs
Share additional feedback to help us improve.
0/255
|
Powered by Aikyam @2025 All rights reserved
+1 866 451 2735
+1 866 451 2735
+1 855 819 5909