Retirement of SAP SuccessFactors Basic Authentication, Employee Central SFAPIs (Except CompoundEmployee), and Legacy People Profile Configuration APIs

SAP SuccessFactors is retiring legacy authentication and API capabilities that impact Oracle Integration customers using SAP SuccessFactors in integrations.

The impacted areas include:

Basic Authentication
SOAP-based Employee Central SFAPIs, except CompoundEmployee
Legacy People Profile Configuration OData V2 APIs

The following topics are covered:

Basic Authentication / SuccessFactors Custom Policy

SAP SuccessFactors is decommissioning API access based on Basic Authentication. This impacts Oracle Integration customers using SAP SuccessFactors Adapter connections with the SuccessFactors Custom Policy and SAP SuccessFactors integrations built with technology adapters that use Basic Authentication. See Deprecation of Basic Authentication for APIs.

For Oracle Integration SAP SuccessFactors Adapter connections, the supported security policy to use is SuccessFactors SAML Bearer Assertion Flow with Username Password Token Support.

SOAP-Based Employee Central SFAPIs

SAP SuccessFactors has deprecated the SOAP-based Employee Central SFAPIs, except for CompoundEmployee. These APIs will be deleted on November 20, 2026. SAP recommends migrating impacted API calls to the corresponding OData APIs where applicable. The CompoundEmployee API remains supported and is not part of this retirement. See Deprecation of Employee Central SFAPIs Except CompoundEmployee API.

Legacy People Profile Configuration APIs

SAP SuccessFactors is also retiring the Legacy People Profile Configuration OData V2 APIs used for the legacy People Profile experience. SAP states that no replacement APIs are available for this functionality. See Deprecation of Legacy People Profile Configuration APIs.

Required Action for Basic Authentication

If you are using Basic Authentication in your integrations, complete the following actions to avoid service disruption:

Identify all SAP SuccessFactors Adapter connections using SuccessFactors Custom Policy.
Identify all SAP SuccessFactors integrations built with technology adapters using Basic Authentication.
Create a new SAP SuccessFactors Adapter connection, or update the existing connection, to use SuccessFactors SAML Bearer Assertion Flow with Username Password Token Support.
Update SAP SuccessFactors integrations built with technology adapters to use a supported authentication method instead of Basic Authentication.
Test and validate all updated integrations before moving them to a production environment.

Migration Steps for SAP SuccessFactors Adapter Connections

Once you have the required SAML configuration details, you can either create a new SAP SuccessFactors Adapter connection or update the existing one so that it uses SuccessFactors SAML Bearer Assertion Flow with Username Password Token Support. For more details, see Create an SAP SuccessFactors Adapter Connection.

Replace Existing Connections in Your Integration

Go to the location of the integration to edit.
- In a project.
  1. In the navigation pane, click Projects.
  2. Select the project name.
  3. Click Integrations .
  4. In the Integrations section, find the integration to edit.
- Outside a project.
  1. In the navigation pane, click Design, then Integrations.
  2. Find the integration to edit.
Select the integration currently using the Basic Authentication-based SAP SuccessFactors Adapter connection.
From the Actions menu, select Configure.
In the Configuration Editor, locate the SAP SuccessFactors Adapter connection and select Replace .
Select the new SAP SuccessFactors Adapter connection that uses SuccessFactors SAML Bearer Assertion Flow with Username Password Token Support.
Click Save.

Refresh Integration Endpoints and Activate the Integration

Go to the location of the integration to refresh and activate.
- In a project.
  1. In the navigation pane, click Projects.
  2. Select the project name.
  3. Click Integrations .
  4. In the Integrations section, find the integration to refresh.
- Outside a project.
  1. In the navigation pane, click Design, then Integrations.
  2. Find the integration to refresh.
Select the updated integration.
From the Actions menu, select Refresh Endpoints.
Confirm that the refresh completes successfully.
Activate the integration.

Technology Adapter Integrations

For SAP SuccessFactors integrations built with technology adapters, update the authentication configuration in the relevant technology adapter to use a supported authentication method instead of Basic Authentication, then retest the integration end to end.

Required Action for SOAP-Based Employee Central SFAPIs

If you are using SOAP-based Employee Central SFAPIs in integrations (except for CompoundEmployee), complete the following actions to avoid service disruption.

Identify all usages of SOAP-based Employee Central SFAPIs except CompoundEmployee.
Migrate affected SOAP-based Employee Central SFAPI calls to the corresponding OData APIs where applicable.
Test and validate all updated integrations before moving them to a production environment.

Required Action for Legacy People Profile Configuration APIs

If you are using Legacy People Profile Configuration APIs in integrations, complete the following actions to avoid service disruption.

Identify all usages of Legacy People Profile Configuration APIs.
Evaluate and plan alternatives for impacted integrations because SAP does not provide replacement APIs.
Test and validate all required changes before moving them to a production environment.

Ensure all required changes are completed before the applicable SAP retirement dates.

Additional Information

Oracle Integration supports the SAP SuccessFactors Adapter with SuccessFactors SAML Bearer Assertion Flow with Username Password Token Support for supported SAP SuccessFactors API scenarios, including OData APIs and the CompoundEmployee API.

See: