OAG Returns 400 Status Code with Plain HTTP Error
Last Updated:
Access Gateway
Okta Classic Engine
Okta Identity Engine
Overview
If Okta Access Gateway (OAG) is behind a load balancer that terminates SSL, accessing OAG applications may result in a 400 Bad Request error page with the following error message:
400 Bad Request - The plain HTTP request was sent to HTTPS port - Access Gateway
Applies To
- Okta Access Gateway (OAG)
Cause
OAG only accepts secure HTTPS traffic on port 443.
If a plain HTTP request is sent on port 80, OAG will redirect the request to HTTPS on port 443 via a 301 redirect response. However, if a plain HTTP request is sent on port 443, this error page is displayed.
Solution
If desired, traffic between OAG and the backend application may use plain HTTP by configuring the application's protected web resource URL accordingly.
