08/10/2023 09:21 AM
Target application is expecting the account creation payload in the following format :
{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:User"
],
"userName": "${user.email}",
"active": true,
"name": {
"givenName": "${user.givenName}",
"familyName": "${user.lastName}"
},
"emails": [{
"value": "${user.email}",
"type": "work"
}]
}
This seems to cause an issue at provisioning time as variables appear to be partly managed:
"ecm-worker","2023-08-10T15:13:36.572+00:00","2023-08-10T15:13:36.547629934Z stdout F 2023-08-10 15:13:36,547 [quartzScheduler_Worker-1] DEBUG rest.RestProvisioningService - Calling Webservice Url - https://url/Users/ with httpParams - [schemas:[urn:ietf:params:scim:schemas:core:2.0:User], userName:usersemail@domain, active:true, name:[givenName:${user.givenName}, familyName:${user.lastName}], emails:[[value:${user.email}, type:work]]]"
Any idea as to what could be the issue?
Thanks in advance!
Solved! Go to Solution.
08/10/2023 09:34 AM - edited 08/10/2023 09:37 AM
Hi @flegare ,
There’s is no ${user.givenName} attribute. Can you try with ${user.firstname} for givenName mapping
{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:User"
],
"userName": "${user.email}",
"active": true,
"name": {
"givenName": "${user.firstname}",
"familyName": "${user.lastName}"
},
"emails": [{
"value": "${user.email}",
"type": "work"
}]
}
08/10/2023 10:28 AM
hi @pmahalle ,
Good eye! I ran into another unrelated issue but this worked. It'd be great if the logs could reflect such issues though
Thanks again!
Francois