Thank you for the recommendation. I will open a new topic maybe transforms would be sufficient after all.
I tried this for example for sAMAccountName
Since I was only testing I set for testFirst and testLast default Values. I later wanted to use these two variables for the first- and lastname with no special characters
[
{
“op”: “replace”,
“path”: “/fields/44”,
“value”: {
“name”: “sAMAccountName”,
“transform”: {
“type”: “rule”,
“attributes”: {
“name”: “Create Unique LDAP Attribute”
}
},
“attributes”: {
“cloudMaxUniqueChecks”: “50”,
“cloudMaxSize”: “20”,
“cloudRequired”: “true”,
“template”: “$(testLast)$(testFirst)$(uniqueCounter)”,
“testFirst”: “Max”,
“testLast”: “Mustermann”
},
“isRequired”: false,
“type”: “string”,
“isMultiValued”: false
}
}
]
Thanks!
Kindly open a new forum and will try to provide more inputs to you.
Below is high level solution which can resolve your Create Profile - Transform issues.
- Create a new identity attribute named as “Initial AD CN”
- Create a transform against the “Initial AD CN” identity attribute
{
“name”: “Concat - InitalADCN”,
“type”: “concat”,
“attributes”: {
“values”: [
{
“type”: “decomposeDiacriticalMarks”,
“attributes”: {
“input”: {
“attributes”: {
“sourceName”: “HRMSSource”,
“attributeName”: “FIRST_NAME”
},
“type”: “accountAttribute”
}
}
},
" ",
{
“type”: “decomposeDiacriticalMarks”,
“attributes”: {
“input”: {
“attributes”: {
“sourceName”: “HRMSSource”,
“attributeName”: “LAST_NAME”
},
“type”: “accountAttribute”
}
}
}
]
},
“internal”: false
}
- ATtach the above transform to the idnetity attr named as :: “Initial AD CN”
- Go to Create Profile of AD source and perform the below mappings inside create profile JSON of AD source for “distinguishedName” account attr
{
“name”: “distinguishedName”,
“transform”: {
“type”: “rule”,
“attributes”: {
“name”: “Create Unique Account ID”
}
},
“attributes”: {
“template”: “CN=$(initialAdCn)$(uniqueCounter),OU=Accounts,OU=Resources,DC=lab,DC=test,DC=com”,
“cloudMaxUniqueChecks”: “50”,
“cloudRequired”: “true”
},
“isRequired”: false,
“type”: “string”,
“isMultiValued”: false
}
5 Save the changes
6. Retest the Joiners flow
Hi @rohit_wekhande I humbly suggest that you are introducing un-necessary complexity (using Identity attributes) simply to avoid using nested Transforms, which, IMHO, would be best practice in this scenario.
Thanks for your perspective! I will revisit my approach.