Okta created the On-prem Connector for Oracle E-Business Suite (EBS) to provide an out-of-the-box solution that connects Oracle EBS on-premises applications with Okta Identity Governance. It enables the discovery, visibility, and management of Oracle E-Business Suite entitlements (Responsibilities) directly within Okta. This integration enhances security, saves time, and simplifies governance by eliminating the need for custom integrations and streamlining entitlement management.
Supported editions: Oracle 12.2.x or later.
This article lists common errors encountered during the setup of the On-prem Connector for Oracle EBS and provides easy troubleshooting suggestions.
Error: Connection timed out: connect
Error: java.net.UnknownHostException: [FQDN address]
Error: Connection refused: connect
Error: Failed to confirm imported users (firstName & lastname - The field cannot be left blank)
Error: Please check and ensure Provisioning Agent is running
Error: http protocol is not supported
Error: Uninstall script not found or not executable
Error: Connection timed out: connect
Cause
-
Incorrect IP address in the Fully Qualified Domain Name (FQDN), specifically the machine's IP address where the On-prem Connector is located.
Solution
-
Verify and provide the correct IP address of the machine where the On-prem Connector is located.
-
Uninstall any unnecessary On-prem Connectors, ensuring only the relevant one is retained.
Error: java.net.UnknownHostException: [FQDN address]
Cause
-
The specified Fully Qualified Domain Name (FQDN) is incorrect or unresolvable. This typically occurs when the FQDN does not correctly point to the machine where the On-prem Connector is located.
-
Examples of FQDNs
-
Valid:
server1.example.com, my-computer.office.local -
Invalid:
-
Partial FQDN: server1 (missing domain)
-
Unresolvable FQDN: not-a-real-server.example.com (does not resolve on the network)
-
-
Solution
-
Ensure that the correct FQDN is provided. Verify the FQDN of the machine hosting the On-prem Connector and update the configuration accordingly.
Error: Connection refused: connect
Cause
-
On-prem Connector is unavailable due to a network interruption, has been uninstalled, or has been manually stopped.
Solution
-
Verify the connectivity of the On-prem Connector and reinstall if necessary.
Error: Failed to confirm imported users (firstName & lastname - The field cannot be left blank)
Cause
-
firstName and lastName are null
Solution
-
Navigate to Directory > Profile Editor, select the User (default) profile, and then modify the firstName and lastName fields to make them optional. This change will prevent issues caused by these fields being empty or not provided.
Error: Please check and ensure Provisioning Agent is running
Cause
-
Okta Provisioning Agent is down or disrupted.
Solution
-
Ensure the Okta Provisioning Agent is active and the machine on which it is running is accessible.
Error: http protocol is not supported
Cause
Okta Provisioning Agent is not configured for HTTP protocol.
Solution
Allow HTTP in OPP Agent by navigating to /opt/OktaProvisioningAgent/conf/
edit OktaProvisioningAgent.conf
and restart the Okta Provisioning Agent. Detailed guidance on restarting the Okta Provisioning Agent is available here.
Error: Uninstall script not found or not executable
Cause
-
The Okta On-prem Connector was installed on Linux using privileged user access (e.g., sudo), but the user is attempting to uninstall it without the necessary elevated privileges.
Solution
-
If the installation was performed using privileged user access, ensure that the uninstallation is also executed with the appropriate elevated privileges.
Error: Config file (.opcconfig) not found in /home/ec2-user/bin. Exiting… while uninstalling OPC agent
Cause
-
Okta On-prem Connector has been installed in a custom path.
Solution
To resolve this issue, navigate to <custom-path>/Atom_atom_* directory and run the ./uninstall command to uninstall the agent.
