Overview

This article explains the expected sign-in logging behavior when using Adaptive ZTNA with different versions of the Timus Connect application and authentication methods.

Depending on the following factors, sign-in events may appear either in the legacy Events page or the newer Sign-In Events page:

• Adaptive ZTNA status
• Timus Connect client version
• Authentication method used

This behavior is expected and by design.

Expected Logging Behavior Matrix

Detailed Behavior Explanation

When Adaptive ZTNA is Disabled

If Adaptive ZTNA is disabled on the tenant:

• All sign-in events are expected to appear under the legacy Events page.
• This behavior remains consistent regardless of:
  • Timus Connect client version
  • Whether the user signs in through the desktop application
  • Whether the user signs in through the My Timus Portal

Expected Result

All authentication activity logs are written to:

Events page (legacy)

When Adaptive ZTNA is Enabled

Once Adaptive ZTNA is enabled, logging behavior changes depending on the client version and authentication flow used.

Timus Connect Version 4.6.12

Desktop Application Sign-In

If the user signs in directly through the Timus Connect desktop application version 4.6.12:

Expected Result

The event is logged under:

Events page (legacy)

My Timus Portal Sign-In

If the user signs in through:

https://my.timusnetworks.com/

while using Timus Connect version 4.6.12:

Expected Result

The event is logged under:

Sign-In Events page

Timus Connect Version 5.0.14

Version 5.x.x introduces support for the newer Adaptive ZTNA sign-in logging workflow.

Desktop Application Sign-In

If the user signs in through the Timus Connect desktop application version 5.0.14:

Expected Result

The event is logged under:

Sign-In Events page

My Timus Portal Sign-In

If the user signs in through:

https://my.timusnetworks.com/

while using Timus Connect version 5.0.14:

Expected Result

The event is logged under:

Sign-In Events page

Important Notes

• This behavior is expected and does not indicate a product issue.
• Adaptive ZTNA alone does not fully determine where end-user logs are written.
• The Timus Connect client version also affects the logging destination for end-user authentication events.
• Version 5.x.x supports the newer Adaptive ZTNA logging workflow more consistently.
• Older client versions may continue utilizing the legacy Events logging system for certain authentication methods.
• Administrator sign-in logging behavior depends solely on whether Adaptive ZTNA is enabled or disabled:
  • If Adaptive ZTNA is disabled, administrator sign-ins are logged under the legacy Events page.
  • If Adaptive ZTNA is enabled, administrator sign-ins are logged under the Sign-In Events page.

Troubleshooting Checklist

If sign-in events are not appearing where expected:

1. Verify whether Adaptive ZTNA is enabled on the tenant.
2. Confirm the Timus Connect client version installed on the device.
3. Determine the authentication method used:
   • Timus Connect desktop application
   • My Timus Portal
4. Validate whether the event should appear under:
   • Events (legacy)
   • Sign-In Events page

Updated May 27, 2026 21:16