Hello, I’m new to ISC and I was wondering how I can synchronize a startDate that is in ISO format with a target account attribute that uses the dd-MM-yyyy format.
Will ISC attempt to resynchronize the date every time because the formats are different?
Thank you very much
Hi @DivyaL_7
You are right , if there is a format mismatch , it will resynchronize , ending up in loop situation .
Thanks
Sid
Hello @sidharth_tarlapally ,
How can we solve this problem please?
I need to sync the dates and not change any format..
thank you
Create a new custom identityAttribute , apply dateFormat to this transform and bring the startDate value in dd-MM-yyyy format .
For attribute sync , use this newly created attribute , instead of startDate directly .
Hello again @sidharth_tarlapally ,
thank you for your reply,
Unfortunately, my client is very strict and does not want us to add the dates as identity attributes….
Are there any alternative solutions please?
Thank you so much.
Umm , I don’t see a way
You should probably explain to the client that syncing is happening from the identity attributes downstream to the account attributes (for the values that you want to keep in a sync). You can have multiple sources, and each source can have an account attribute of a date which will be overwritten from certain identity attribute (e.g. date in your case) during the sync.
Hello @markomanium ,
Thank your for your reply,
We explained it to them however they simply do not want the newly created identity attribute to be visible on the identity… For them, it is not compliant with their IAM standards to display account attributes on the identity. Is there a way to hide the newly created identity attribute for showing on the identity? Or are there no alternatives to this?
Many thanks,
I couldn’t find much on this except the topic: Mask sensitive identity attributes - Identity Security Cloud (ISC) / ISC Discussion and Questions - SailPoint Developer Community
In other words, including encryption in the provisioning rules..
The concept of Attribute Sync is to push an authoritative value to the target application. If we create a formatted Identity Attribute, only then, we can update that value on the end system.
is it acceptable to bring startDate in the dd-MM-yyyy format?
From what I see, these are the only two viable options, and there doesn’t appear to be an ideal workaround.
What kind of connector is this for? If you can’t use identity profile attribute, I can think of 2 options. Modify provisioing policy or before prov rule to transform your date format to send on modify op and set it to the attribute request in question
Hello, thank you for your reply,
It’s a web connector source
Hello thanks for your reply,
The client unfortunately wants to keep startDate in ISO format
Hi @DivyaL_7 ,
Are you referring to this as a one-time activity during account creation, or do you need the attribute to be updated whenever it changes ?
Hi @UjjwalJain ,
I need the account attribute to update each time the identity attribute changes
To reiterate, it’s not possible to sync different formats, you’d have to create an identity attribute with the proper format and use that to sync downstream.