OAG: Applications Are Not Accessible

Okta Access Gateway (OAG) applications become inaccessible and display an HTTP 400 error when a load balancer routes a request to a new node that an administrator has not yet configured as a worker node. Deploy the new node and add it as a worker node in the management console to resolve this issue.

When accessing the application in a browser, the following error appears:

ERROR: Reading content from file: /opt/oag/configs/spgw/config/spgw.json

• Okta Access Gateway
• High Availability
• Okta Identity Engine (OIE)
• Okta Classic Engine

This error occurs when a load balancer routes a request to a new node that an administrator has not yet added as a worker node. The node lacks the configuration required to serve the requested application, which prompts Okta to generate the HTTP 400 error message.

How is the HTTP 400 error resolved for inaccessible applications?

Deploy the new node and add it as a worker node, then validate its state by navigating to the High Availability section in the management console.

1. Log in to the management console.
2. Go to 5.System > 8.High Availability.
3. Review the section to confirm the node state:
   • Access Gateway High Availability Setup (Single) displays when the node operates independently of a cluster.
   • Access Gateway High Availability Setup (Worker) displays for a worker node.
   • Access Gateway High Availability Setup (Admin) displays for the admin node.

NOTE: Administrators do not need to perform the Admin UI initialization step and Identity Provider (IdP) configuration during the deployment steps for worker nodes.