Symptom
You are currently implementing Employee Central Services Center (ECSC) and wish to learn how to include SAP IAS in your landscape for authentication purposes
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Environment
- SAP SuccessFactors - Employee Central Service Center
- SAP Business Technology Platform
Cause
Resolution
You can configure IAS to login to SuccessFactors, then follow the ECSC implementation guide (below under See Also)
“Extension Center” will automatically create “Application Identity Provider” in BTP Neo-> Security -> Trust. Here the “application Identity Provider” is SF IDP not IAS, although you are configuring IAS to login SuccessFactors, see below:
IMPORTANT:
One limitation of ECSC is: If you want to manually create “Application Identity Provider” and specify IAS(instead of SF IDF) as “Application Identity Provider” in BTP Neo-> Security -> Trust, then ECSC will not work. There are many reasons for this limitation (for example, if you configure “Global User ID” as the unique ID of User. To call SuccessFactors API from ECSC, additional property “tokenService.body.primaryemployment” should be supported by BTP destination. However, Neo destination doesn’t support “tokenService.body.primaryemployment”).
See Also
SAP SuccessFactors Employee Central Service Center Implementation Sequence | SAP Blogs
IAS integration with SAP SuccessFactors Application – 1 | SAP Blogs
Keywords
ECSC, Employee Central Services Center, Services Center, Services Centre, SAP IAS, IAS, BTP, SCP, Your User Profile is not configured, authentication , KBA , LOD-SF-INT-AHR , Ask HR - Employee Central Service Center (ECSC) , LOD-SF-INT , Integrations , How To
Product
Attachments
e26c2b5e4781429856e3f3de436d43d6 |