Documentation

SSO idle session timeout not working in AEM

Last update: Wed Sep 24 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

In Adobe Experience Manager (AEM) - On-Premises, the idle session timeout doesn’t work when logging in through a custom Single Sign-On (SSO) setup. The issue doesn’t occur with AEM’s default login mechanism. To resolve the issue, review and adjust your custom SSO configuration.

Description description

Environment

  • Product: Adobe Experience Manager (AEM) On-Premises, v6.5.21.0
  • Instance: Development

Issue/Symptoms

When using a custom Single Sign-On (SSO) implementation with AEM, the idle session timeout doesn’t work as expected. Specifically:

  • When accessing AEM through the DNS URL that redirects to the custom SSO login page, sessions remain active beyond the configured idle timeout.
  • The issue doesn’t occur when using the default AEM login mechanism via IP; in this case, sessions expire as expected after the idle timeout.
  • Continuous pulse.data.json network requests are sent every minute. These requests appear to keep the session active.

Resolution resolution

This issue is caused by the custom Single Sign-On (SSO) implementation and not by AEM itself. To resolve the idle session timeout behavior:

  1. Verify Login Behavior

    • Sessions expire correctly when using AEM’s default login via IP.
    • Sessions remain active when logging in through a DNS URL that redirects to a custom SSO login page.

  2. Understand pulse.data.json Activity

    • AEM sends periodic requests topulse.data.json (about once per minute) to support live notifications and workflow updates.
    • These requests may reset the idle timer if not properly handled by the SSO configuration.
    • The small red button in the top-right corner of the AEM UI uses this endpoint to display inbox items.

  3. Recommended Actions

    • Review the custom SSO setup with your internal team.
    • Ensure the SSO configuration accounts for periodic system requests like those from pulse.data.json, which are essential for maintaining certain functionalities in AEM
    • Do not block or disable pulse.data.json, as doing so will disrupt key authoring and notification functionalities.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f