Symptom
NOTE: This KBA is only for SF OData API v1. If you are using SF SCIM API v2, there is no $.personKeyNav.
In IPS, SuccessFactors is set as a source system, and Identity Authentication (IAS) is set as the target system. The sync job is failing with one of the following error messages:
Exception: Source path: $.personKeyNav.userAccountNav.username is not available in content, but is required in defined system transformation Caused by: com.sap.security.iag.provisioning.mapping.MandatorySourcePathNotFoundException
Caused by: com.jayway.jsonpath.PathNotFoundException: Missing property in path $['personKeyNav']['userAccountNav']
Exception: Source path: $.personKeyNav.userAccountNav.sapGlobalUserId is not available in content, but is required in defined system transformation Caused by: com.sap.security.iag.provisioning.mapping.MandatorySourcePathNotFoundException: Source path: $.personKeyNav.userAccountNav.sapGlobalUserId is not available in content, but is required in defined system transformation Caused by: com.jayway.jsonpath.PathNotFoundException: No results for path: $['personKeyNav']['userAccountNav']['sapGlobalUserId'],
Read more...
Environment
- Identity Provisioning
- Identity Authentication
- SAP SuccessFactors
Product
Keywords
IPS, SuccessFactors, Allow Admin to Access OData API through Basic Authentication, User Account OData entity, IPSADMIN, personKeyNav.userAccountNav.username, not available in content , KBA , BC-IAM-IPS , Identity Provisioning Service (IPS) , LOD-SF-PLT-IAS , Identity Authentication Services (IAS) With BizX , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview