Timestamp on forwarded Idp audit log data is off by 5 minutes

    Applies to:
  • Legacy SecureAuth IdP
Deployment model:
  • On Premises
  • SecureAuth IdP Versions Affected: All Versions

    Description: We are forwarding an instance of SecureAuth log audit data for several applications to a SYSTEM Log/SIEM. When looking at the log data from SIEM side the time is off by 5 minutes.

    Cause: The issue is caused by queuing delays on SIEM side.

    Resolution: Activate the "Text" option for Audit Logs under Logs tab for your desired realm. A new Audit log will be created in D:\Secureauth\SecureAuth<Your Realm Number>\AuditLogs directory. Afterward you can compare the timestamp of the lines in new Audit log and the same lines in SIEM.


    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.
    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful



    Please sign in to leave a comment.