<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
Okta Access Gateway: Application Getting CORS Error After Session Expiration
Okta Classic Engine
Access Gateway
Overview
Once OAG session gets expired, the application gets CORS error when user submits a form.
Applies To
  • Okta Access Gateway
Cause
The issue can happen because of how Javascript handles the page refresh. It does an api call and gets a redirect link after expiration but is not designed to send it to the browser. The request then fails with CORS error and since the it has not received at the browser end, the login flow does not get initiated. 
Solution
There are a couple of workarounds that can be implemented: 
  • Increase session timeout or use the browser session expiration setting for the application.
  • Use the Extend AJAX session policy in OAG application.
Loading
Okta Access Gateway: Application Getting CORS Error After Session Expiration