Frequent Calls to "oagNPSessionIntrospect" in Okta Access Gateway

Frequent calls to the /oagNPSessionIntrospect-b51ce026-f27f-44af-b65d-1dd9c24f00ff/index.html resource occur when accessing an Okta Access Gateway (OAG) application due to an Advanced Policy configured to extend Asynchronous JavaScript and XML (AJAX) session handling. Resolve this by removing the policy or increasing the timeout value to reduce the call frequency. When reviewing a Developer Tools or HTTP Archive (HAR) trace, frequent calls appear regularly.

The following image displays the frequent calls to the resource in a Developer Tools trace.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Okta Access Gateway (OAG)

An Advanced Policy configured in the OAG application to extend AJAX session handling causes these calls. The associated script executes on a defined interval to check if a user session is inactive. When a user session expires, the script alerts the user and refreshes the page. The user then receives a new session if an Okta session exists, or Okta prompts the user to reauthenticate. The internal scripts involved in this policy specifically call the /oagNPSessionIntrospect-b51ce026-f27f-44af-b65d-1dd9c24f00ff/index.html resource.

How is the frequent call behavior managed?

These calls do not indicate a problem, and no action is required. Review the Advanced Access Gateway policy examples documentation to understand the purpose of this policy.

Manage the extended AJAX session handling by removing the policy or increasing the timeout value.

• Remove the respective policies if the extended AJAX session handling causes problems or is unnecessary.
• Increase the oagSMTimeoutSeconds value in the respective policies to maintain the extended AJAX session handling, but reduce the frequency of the calls. This parameter defines the frequency in seconds to run the script to check the session.