An incorrectly configured EBS_USER header in the Okta Access Gateway (OAG) application causes an access service error when accessing an Oracle E-Business Suite (EBS) application. Configure the EBS_USER header attribute with a valid username to resolve the error. When accessing an Oracle EBS application in Okta Access Gateway, the application generates the following error message:

EBS Access Service is not Available: Status code:400
EBS_USER HEADER IS REQUIRED

• Okta Classic Engine
• Okta Identity Engine (OIE)
• Okta Access Gateway (OAG)
• Oracle E-Business Suite (EBS)

The EBS_USER header is incorrectly configured in the Okta Access Gateway application.

How is the EBS_USER header configured?

Navigate to the Oracle EBS Single Sign-On (SSO) Agent application in the Okta Access Gateway Admin UI and configure the EBS_USER header attribute with a valid username.

1. Access the Okta Access Gateway Admin UI.
2. Navigate to the Oracle EBS SSO Agent application.
3. Select the pencil icon to edit the application.
4. Select the Attributes tab.
5. Add or edit the username attribute with a value that exists in Oracle EBS. Ensure the following options are configured:
   • Data Source: Select IDP, or select Static if testing with one username value.
   • Field: Enter appuser.userName.
   • Type: Select Header.
   • Name: Enter EBS_USER.

Related References

• Configure the EBS SSO Agent (Rapid) application