Symptom
- Onboardees are not being created in the Identity Authentication Service (IAS), and the real-time log indicates "entity skipped".
- Onboardees appear as "unknown" in the onboarding dashboard.
- Logs would show as
- Details of Integration Process Error: Unable to parse oauth token response due to HTTP operation failed invoking.... with statusCode: 401; click to download server response
- Failed to generate access token using refresh token. Trying again with credentials.
Environment
SAP SuccessFactors Onboarding
Reproducing the Issue
- Search for onboardee in the onboarding dashboard; onboardee name appears as "unknown".
- Search for the user in IAS; user does not exist.
- Check the real-time sync log; onboardee creation shows as "entity skipped".
Cause
- Integration issue caused by the inability of the token endpoint to parse OAuth tokens when special characters are used in the client_secret.
- Conditions in the target transformation are not fulfilled, preventing user provisioning.
Resolution
- Please have your Integration Partner correct or use a client_secret which does not contain special characters. Or check with the credentials token as mentioned with the error logs.
- Verify and correct the credentials token as mentioned in the error logs.
- Review the target transformation conditions in the IAS provisioning configuration.
- Perform the following steps after correcting the configuration:
- Refresh OData.
- Save and activate the process variant being used by onboardees
- Update process flows for onboarding, ensuring an admin service user is selected.
See Also
Keywords
obx, IAS provisioning, entity skipped, onboarding dashboard unknown, oauth token error, client_secret special characters, IPS provisioning job, SAP SuccessFactors onboarding, target transformation conditions, user provisioning failure, real-time sync log , KBA , LOD-SF-OBX-IAS , IAS User Authentication , Problem
Product
SAP SuccessFactors Onboarding all versions
SAP Knowledge Base Article - Public