OAG: Application JS Files Not Getting Loaded through OAG
Last Updated:
Access Gateway
Okta Classic Engine
Okta Identity Engine
Overview
Issue Symptoms:
- Application not rendering successfully through Okta Access Gateway (OAG).
- Browser developer tools show a 403 error for some JavaScript files.
- The calls to the other resources work fine.
- The issue persists even after setting NO_AUTH for the application.
No issues were found when the same request to the failing JavaScript file was tried in another browser tab, through curl, or when the request was not going through OAG.
Applies To
- Okta Access Gateway (OAG)
Cause
The OAG application was set up to send a private domain as a host header, but the backend JavaScript files were expecting a public domain. Because of this, rendering failed through OAG, and the direct access (through browser or curl) to the failing JavaScript files worked.
The issue can also happen with resources other than JavaScript files.
Solution
- Edit the application in OAG Admin UI.
- Go to the advanced section and enable Public domain for host header. If OAG load balancing is enabled then the same can be done from Protected Web Resource section.
- Save the application.
