Troubleshooting

Review common Enterprise Connector and OAuth 2.0 issues and their recommended resolutions.

Enterprise Connector not connecting

  • Verify that the enterprise location is provisioned in ION.
  • Confirm that the Enterprise Connector version is 2020-08 or later.
  • Check that the Enterprise Connector service is running at the designated location.
  • Verify outbound network connectivity from the Enterprise Connector environment to the cloud.

Enterprise Connector status is Red (PENDING / NOT EXISTED)

  • The Enterprise Connector has not been installed at the enterprise location.
  • Deploy an API suite to trigger automatic Enterprise Connector installation.
  • See the Infor ION User Guide for provisioning instructions.

Enterprise Connector status is Red (UNSUPPORTED / UNKNOWN)

  • The installed Enterprise Connector version is too old to support API Gateway Hybrid Services.
  • Upgrade Enterprise Connector to version 2020-08 or later.

OAuth 2.0 token acquisition fails with invalid_client

  • Verify that the client ID and client secret are correct and have not been rotated by the external service.
  • Confirm that the token URL points to the correct authorization server endpoint.
  • Check whether the external service expects client credentials in the request body instead of the Authorization header.

OAuth 2.0 token acquisition fails with invalid_grant (ROPC)

  • Verify that the username and password are correct.
  • Check whether the user account has been locked or disabled.
  • Confirm that the external service still supports the Resource Owner Password Credentials (ROPC) grant type.

OAuth 2.0 outbound requests fail with HTTP 401 after initial success

  • The external service might have revoked the token or reduced the token lifetime.
  • Verify that the token endpoint is reachable from the Hybrid Service.
  • Review the Hybrid Service logs for token refresh failures.

OAuth 2.0 configuration does not take effect

  • Ensure that you clicked Save after configuring OAuth 2.0 Target Security.
  • Verify that Enterprise Connector is enabled for the endpoint.
  • If credentials were changed recently, the new credentials are used during the next token refresh cycle.

Hybrid Service cannot reach the token endpoint

  • Verify that the token URL is correct and accessible over HTTPS from the customer environment.
  • Check firewall rules and proxy settings for outbound connectivity from the Hybrid Service.
  • Ensure that the token endpoint uses a valid and trusted TLS certificate.