Action Required: Retirement of SAP SuccessFactors Basic Authentication, Employee Central SFAPIs, and Legacy People Profile APIs

SAP SuccessFactors is retiring Basic Authentication and certain APIs used by Oracle Integration customers. If your integrations use affected SAP SuccessFactors authentication methods or APIs, complete the required changes before the applicable SAP retirement dates to avoid disruption.

Attention Oracle Integration Customers Using SAP SuccessFactors

This blog applies to integrations that use:

• SAP SuccessFactors Adapter connections with SuccessFactors Custom Policy. 
• SOAP-based Employee Central SFAPIs except CompoundEmployee.
• Legacy People Profile Configuration OData V2 APIs.

Problem Statement

SAP SuccessFactors is retiring the following:

• Basic Authentication: Affects SAP SuccessFactors Adapter connections using SuccessFactors Custom Policy and technology-adapter integrations that use Basic Authentication. The retirement date is November 20, 2026. See Deprecation of Basic Authentication for APIs.
• SOAP-based Employee Central SFAPIs except CompoundEmployee: SAP will delete these APIs on November 20, 2026. SAP recommends migrating affected calls to corresponding OData APIs where applicable. See Deprecation of Employee Central SFAPIs Except CompoundEmployee API.
• Legacy People Profile Configuration OData V2 APIs: The end of maintenance was May 15, 2026. SAP will delete these APIs on November 13, 2026. SAP does not provide replacement APIs. See Deprecation of Legacy People Profile Configuration APIs.

Impact on Existing Integrations

If no action is taken:

• Integrations using Basic Authentication will stop working after SAP deletes API access based on Basic Authentication.
• Integrations using SOAP-based Employee Central SFAPIs except CompoundEmployee will stop working unless they are migrated to corresponding OData APIs where applicable before November 20, 2026.
• Integrations using Legacy People Profile Configuration APIs will stop working unless they are redesigned before November 13, 2026 because SAP does not provide replacement APIs.

Required Action

For Basic Authentication

1. Identify all SAP SuccessFactors Adapter connections using SuccessFactors Custom Policy and all technology-adapter integrations that use Basic Authentication.
2. Move affected SAP SuccessFactors Adapter connections to SuccessFactors SAML Bearer Assertion Flow with Username Password Token Support. See Create a Connection for SAP SuccessFactors Adapter.
3. Update technology adapter integrations to use a supported authentication method instead of Basic Authentication.
4. Test and validate the updated integrations.
5. Move the validated changes to production before November 20, 2026.
   

For SOAP-based Employee Central SFAPIs except CompoundEmployee

1. Identify all usages of SOAP-based Employee Central SFAPIs except CompoundEmployee.
2. Migrate affected SOAP-based Employee Central SFAPI calls to corresponding OData APIs where applicable, as described in Deprecation of Employee Central SFAPIs Except CompoundEmployee API.
3. Test and validate the updated integrations.
4. Move the validated changes to production before November 20, 2026.

For Legacy People Profile Configuration OData V2 APIs

1. Identify all usages of Legacy People Profile Configuration OData V2 APIs.
2. Evaluate and plan alternatives for the affected API usage because SAP does not provide replacement APIs. See Deprecation of Legacy People Profile Configuration APIs.
3. Redesign the affected integrations as needed.
4. Test and validate the updated integrations.
5. Move the validated changes to production before November 13, 2026.

For detailed migration guidance, see Retirement of SAP SuccessFactors Basic Authentication, Employee Central SFAPIs (Except CompoundEmployee), and Legacy People Profile Configuration APIs.

Conclusion

Avoid integration disruption by identifying and updating affected SAP SuccessFactors integrations before the applicable retirement dates.