Click HERE to see how Saviynt Intelligence is transforming the industry. |
04/12/2022 01:07 PM
Hi Team,
Can any one please guide how to pass update proxyAddresses attribute in below format
"SMTP:flastname@abc.com","smtp:flastname1@abc.com"
Thanks,
Sitarasmi
Solved! Go to Solution.
04/12/2022 02:24 PM
Hi Sitarasmi,
Please find below a sample that might help you passing proxyAddresses through AD connector :
{ "proxyaddresses":["SMTP:${user.firstname.substring(0,1)}${user.lastname}@abc.com","smtp:${user.firstname.substring(0,1)}${user.lastname}1@abc.com"] }
I simplified the code to match your example
Best,
Adrien.
04/12/2022 02:24 PM
Thanks Adrien, it helped.
Just one query - for some attributes, which are mapped but don't have any data are shown as null in AD
Eg - title filed - we are not passing any value currently, but maintaining it in createaccountjson in AD. The value in AD is shown as null. This value will be passed in future.
we want to show it as empty in AD
Could you please guide how to achieve it.
04/12/2022 02:24 PM
Hi Sitarasmi,
In your CREATEACCOUNTJSON or UPDATEACCOUNTJSON, just simply mention an empty value as below, where we push the user's title if it is valued, else it sends an empty value.
{ "title":"${null!=user.title?user.title:''}" }
... and don't forget to set the SUPPORTEMPTYSTRING parameter as "FALSE" to make sure the data is being removed on your target AD (as specified in the documentation) : https://saviynt.freshdesk.com/support/solutions/articles/43000578581-active-directory-ad-connector-g...
Hope this helps too.
Best,
Adrien.
04/12/2022 02:24 PM
Thank you very much Adrien, its working.
Regards,
Sitarasmi
04/12/2022 02:24 PM
Hi Adrien,
The empty string worked for AD connection JSON, when i tried same with email notification template, its not working.
can you please guide how to handle null value in notification.
Thanks in Advance,
Sitarasmi
04/12/2022 02:24 PM
Hi Sitarasmi,
I answered to this query through this ticket : https://saviynt.freshdesk.com/support/discussions/topics/43000527012.
Please consider opening a separate ticket for each use case so that everyone has an enhanced and efficient research while looking for solutions :-).
Regards,
Adrien.
04/12/2022 02:24 PM
sure, will raise separate queries !
Thanks,
Sitarasmi