Security Events

Modified on Fri, 08 Dec 2023 at 10:03 AM

On all instances the first step is gaining access or logging in and often than not users may come across moments where they are unable to login. With that in mind, support from administrators is key to assessing the login events.  


In Fluid, the security events page allows administrators to view usage data for user logs. Providing a breakdown of the login data to assist administrators diagnose user login patterns where users may experience failure in logging in to an instance. 


In this article we will explain how to access the security events page including scenarios on how to assess the login data. 



Accessing Security Events page


To access the page, simply navigate to the Administration Console page and select the Security Events option under the User Management section. 





Using the Security Events function


The security events page provides detailed information about each login event, including timestamps, identities, and relevant context. 



The Scenario: as a user administrator, a new user (Benjamin) contacts you for assistance about not being able to login for the first time. 

The security events page will allow you to review which login option was used when the login process failed.



The scenario result


In the events page, the first step is to use the search field to enter the new user's name and search for more details. You can search by using either the user's name or registered email address. 



The result from the search will provide you with the login data that is analysed to get to the root cause of the login failure with the following fields:

  • Timestamp - the time that the event occurred. 
  • Identity - the user's username. 
  • Event Type - the type of login method that was used. 
  • Area -  the page that the event occurred
  • Path - route taken during the login attempt
  • Data - the status of the login attempt (success or failure) or account name


In the image below, the event type that was picked up from the login failure was classified as a password login from Benjamin's login attempt. 


Note: there are 3 different login methods that can be identified, namely: Single Sign On, One time pin and Password login. 





In this example as the user administrator, you will review the user's account to verify that their details are correct and inform them to reset their password or to login using an alternative login method such as a One Time Pin (OTP).



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article