Hi,
I am trying to add a custom attribute to the AD adapter (using Verify SaaS only, no IVIG), but I cannot get it to be populated when I provision a user.
I assumed I only need the targetProfile.json file if I'm using Verify SaaS, because recreating the JAR file with only that inside still got me a functioning adapter: after publishing it, I could successfully triggering provisioning. Please let me know if I'm wrong.
So, I created a custom attribute in AD called "custAttr", and I tried adding all of "custAttr", "ercustAttr" and "erADcustAttr" in the targetProfile.json file as follows, inside the "userExtension"->"definition"->"attributes" array:
{
"name": "custAttr",
"type": "string",
"multiValued": false,
"description": "custAttr",
"required": false,
"caseExact": false,
"mutability": "readWrite",
"returned": "default",
"uniqueness": "none",
"specialFlags": "none"
},
I uploaded the modified profile to Verify SaaS, created an application and added the attribute mapping "preferred_username -> custAttr".
I added a user to be entitled and the AD account was successfully created, however the "custAttr" attribute was not populated on AD. (Other non-custom attributes were working fine, and I could also manually set "custAttr" of the provisioned user via PowerShell.)
I tried finding answers in the Adapter Customization Guide, but it didn't help.
Does anyone know what I could be doing wrong? And how the mapping is done between the "er" or "erAD" prefixed attributes and the attributes of AD?
Any help is much appreciated!
Kind Regards,
Gergo