Add an Oracle EBS Application

1. Navigate to your Access Gateway InstanceAn instance, or computer instance, is a virtual machine (VM) or individual physical computer, used to host a software appliance..

   

   Note

   Access Gateway creates a default self-signed certificate. For non-production deployments, this will be appropriate. Proceed past any security exceptions raised by your browser. For production deployments, a valid certificate can be installed and these exceptions will not be needed.

2. In the Access Gateway Admin UI, sign in as as administrator.

3. Click the Applications tab.

   

4. Click +Add to add a new application.

   

    

5. Select one of Oracle EBS R12.1,Oracle EBSR12.2 or Oracle EBS SSO AgentA software agent is a lightweight program that runs as a service outside of Okta. It is typically installed behind a firewall and allows Okta to tunnel communication between an on-premises service and Okta's cloud service. Okta employs several agent types: Active Directory, LDAP, RADIUS, RSA, Active Directory Password Sync, and IWA. For example, users can install multiple Active Directory agents to ensure that the integration is robust and highly available across geographic locations. from the left column menu, and click Create.
   
   

   

   Note

   Please see the Supported Applications section in Okta Access Gateway Supported Technologies support matrix for supported applications and software versions.

The steps that follow then vary based on whether you are creating a Classic or Rapid EBS application.

The following steps describe how to create an EBS Classic Application

1. In the Essentials pane enter:
   

   Field	Value
   Label	The name of the application, as shown in your Okta Tenant.
   Public Domain	The externally facing URL of the EBS application. For example: https://ebs-external.<gateway.info>
   Protected Web Resource	The URL and port combination of the Oracle EBS Implementation being protected. For example: http://ebs122.oracle.com:8000
   Post Login URL	Browseable route-through location to pick up the required EBS cookie from Okta Access Gateway and pass along to the Oracle EBS implementation. For example https://https://ebs-external.<gateway.info>/accessgate/dossologin
   Group	The group containing users who can access the EBS instance.

2. Click Next.
   The Application Configuration pane displays.

3. In the Application Configuration pane enter:

   Field	Value
   Access Gate URL	The EBS URL, matching the protected resource in the prior step using port 6801 For example: http://ebs122.oracle.com:6801
   OID Datasource	Enabled.
   OID Host	Fully qualified host name of the OID Host. For example: oidhost.oracle.com
   OID Port	Port for the OID Host, typically 3060.
   User Search Attribute	CN
   Matching Attribute	EBSUSER,

   Click Next when complete. The Attributes pane will display.

4. In the Attributes tab, using the icon, create the following two attributes.

   For detailed information on the attribute options, see Application Attributes .

   Data Source	Field	Type	Name
   IDP(Okta)	cn	Header	USER_NAME
   oid	orclguid	Header	USER_ORCLGUID

   1. Click the (+) icon

   2. From the Data Source drop down select oid.

   3. From the Field drop down select one of the required fields.

   4. From the Type drop down select the appropriate target type, either Header.

   5. In the Name field enter the associated name for the cookie value expected by Oracle EBS.
      

   6. Click Okay when the attribute is complete.

   7. Repeat to create the two required attributes.

   Click Done when complete.
   

The following steps describe how to configure an EBS Rapid Application

1. In the Essential pane enter:

2. Field	Value
   Label	The name of the application, as show in your Okta Tenant.
   Public Domain	The externally facing URL of the EBS application. For example: https://ebs-external.example.com
   Post Login URL	URL of the EBS server of the form: https://ebs.example.com:8000/OA_HTML/OA.js?OAGFunc=OAHOMEPAGE Note Tje domain portion of the url, 'example.com' must match the domain portion in the Public Domain field.
   Group	The group containing users who can access the EBS instance.

3. Click Next.
   The Application Configuration pane displays.

4. In the Application configuration pane enter:

   Field	Value
   EBS Service Account	The EBS Username or email
   EBS Service Account Password	Password associated with EBS Service Account
   EBS User Identified	Either USER_NAME or EMAIL_ADDRESS
   DBC File Contents	DBC file contents, as provided by the Oracle EBS Administrator,

   Click Not validated when complete.
   
   If all values are entered correctly the Not Validated button will change to green/Validated.
   

5. Click Next

6. In the Attributes tab, using the (+) icon, create the following two attributes.

   For detailed information on the attribute options, see Application Attributes .

   Data Source	Field	Type	Name
   static	User profile field representing user id	Header	EBS_USER
   static	Auth Context	Header	REMOTE_IP
   static	Auth Context	Header	SESSION_ID

   1. Click the (+) icon

   2. From the Data Source drop down select static.

   3. From the Field drop down select one of the required fields.

   4. From the Type drop down select the appropriate target type, either Header.

   5. In the Name field enter the associated name for the cookie value expected by Oracle EBS.
      

   6. Click Okay when the attribute is complete.

   7. Repeat to create the all required attributes.

   Click Done when complete.