Symptom
IAS is a target system in IPS job. In the IAS properties, ias.api.version has been changed from 1 to 2 possibly to fix another issue such as with kba 3104314 - TImeout in IPS job when provisioning Azure groups with large membership. A job fails with similar error:
"errorMessage": "\nuser:Pxxxxxx,\n\nsystem=Identity Authentication - <IAS_TenantID> - target,\n\nerror=org.apache.camel.http.common.HttpOperationFailedException: HTTP operation failed invoking https://<IAS_TenantID>.accounts.ondemand.com/scim/Users/Pxxxxxx with statusCode: 400, Response: {\n \"status\" : \"400\",\n \"schemas\" : [ \"urn:ietf:params:scim:api:messages:2.0:Error\" ],\n \"detail\" : \"Invalid user attribute: sourceSystemId\"\n},\n\ncontent=.......
or
"errorMessage": "\nuser:xxxx\n\nsystem=Identity Authentication - <IAS_TenantID> - target,\n\nerror=org.apache.camel.http.common.HttpOperationFailedException: HTTP operation failed invoking https://<IAS TenantID>.ondemand.com/scim/Users with statusCode: 400, Response: {\n \"status\" : \"400\",\n \"schemas\" : [ \"urn:ietf:params:scim:api:messages:2.0:Error\" ],\n \"detail\" : \"Invalid user attribute: sourceSystem\"\n}....
Environment
Identity Provisioning
Reproducing the Issue
Run IPS job with IAS as target
Cause
IAS has different json configurations for IPS depending on the API (Connector) version being used. Older API v1 json is being used and is not compatible with API v2.
Resolution
Follow the steps from Update Connector Version
to correctly change the API version and have the correct json transformations for that API version.
See Also
Keywords
timeout, SCIM API version , KBA , BC-IAM-IPS , Identity Provisioning Service (IPS) , Problem