Important information

Review important operational information about Enterprise Connector lifecycle, OAuth 2.0 token refresh, and backward compatibility.

Automatic service lifecycle

  • The Enterprise Connector service is installed automatically when the first API suite is deployed to an enterprise location.
  • The Enterprise Connector service is uninstalled automatically when the last API suite associated with the enterprise location is removed.
  • If Enterprise Connector is upgraded while it is running, the Hybrid Service is upgraded automatically.

OAuth 2.0 token refresh strategy

  • The Hybrid Service refreshes access tokens before they expire to help prevent request failures.
  • If the token endpoint is temporarily unavailable, the Hybrid Service retries the request by using a backoff strategy.
  • If the provided credentials are invalid, the Hybrid Service returns an error and does not retry indefinitely.

OAuth 2.0 backward compatibility

  • Existing Enterprise Connector endpoints that use Anonymous, API Key, Basic, JWT Target Authentication, OAuth 1.0a, or WS-Security Username Token continue to work without modification.
  • OAuth 2.0 Target Security is an additional authentication option and does not replace existing target security methods.
  • You can switch an endpoint between OAuth 2.0 Target Security and another target security method without re-creating the endpoint.