![\"\"](\"https:\/\/www.europesays.com\/germany\/wp-content\/uploads\/2026\/06\/image-2-1024x576.png\")
<\/p>\n<\/p>\n
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.<\/p>\n
Attention Oracle Integration Customers Using SAP SuccessFactors<\/p>\n
This blog applies to integrations that use:<\/p>\n
SAP SuccessFactors Adapter connections with\u00a0SuccessFactors Custom Policy.\u00a0<\/p>\n
SOAP-based Employee Central SFAPIs except\u00a0CompoundEmployee.<\/p>\n
Legacy People Profile Configuration OData V2 APIs.<\/p>\n
Problem Statement<\/p>\n
SAP SuccessFactors is retiring the following:<\/p>\n
Impact on Existing Integrations<\/p>\n
If no action is taken:<\/p>\n
Integrations using Basic Authentication will stop working after SAP deletes API access based on Basic Authentication.<\/p>\n
Integrations using SOAP-based Employee Central SFAPIs except\u00a0CompoundEmployee\u00a0will stop working unless they are migrated to corresponding OData APIs where applicable before\u00a0November 20, 2026.<\/p>\n
Integrations using Legacy People Profile Configuration APIs will stop working unless they are redesigned before\u00a0November 13, 2026\u00a0because SAP does not provide replacement APIs.<\/p>\n
Required Action<\/p>\n
For Basic Authentication<\/p>\n
Identify all SAP SuccessFactors Adapter connections using\u00a0SuccessFactors Custom Policy\u00a0and all technology-adapter integrations that use Basic Authentication.<\/p>\n
Move affected SAP SuccessFactors Adapter connections to\u00a0SuccessFactors SAML Bearer Assertion Flow with Username Password Token Support. See\u00a0Create a Connection for SAP SuccessFactors Adapter<\/a>.<\/p>\n Update technology adapter integrations to use a supported authentication method instead of Basic Authentication.<\/p>\n Test and validate the updated integrations.<\/p>\n Move the validated changes to production before\u00a0November 20, 2026.<\/p>\n For SOAP-based Employee Central SFAPIs except\u00a0CompoundEmployee<\/p>\n Identify all usages of SOAP-based Employee Central SFAPIs except\u00a0CompoundEmployee.<\/p>\n Migrate affected SOAP-based Employee Central SFAPI calls to corresponding OData APIs where applicable, as described in\u00a0Deprecation of Employee Central SFAPIs Except CompoundEmployee API<\/a>.<\/p>\n Test and validate the updated integrations.<\/p>\n Move the validated changes to production before\u00a0November 20, 2026.<\/p>\n For Legacy People Profile Configuration OData V2 APIs<\/p>\n Identify all usages of Legacy People Profile Configuration OData V2 APIs.<\/p>\n Evaluate and plan alternatives for the affected API usage because SAP does not provide replacement APIs. See\u00a0Deprecation of Legacy People Profile Configuration APIs<\/a>.<\/p>\n Redesign the affected integrations as needed.<\/p>\n Test and validate the updated integrations.<\/p>\n Move the validated changes to production before\u00a0November 13, 2026.<\/p>\n![\"\"](\"http:\/\/blogs.oracle.com\/integration\/wp-content\/uploads\/sites\/109\/2026\/06\/image-7.png\")
<\/p>\n