Best Practices on Storing Identity data with technical values needed for provisioning

[adriencosson]

Hi folks,

We want to enable creation / update of identities in Saviynt for externals.

As part of their attributes, there are a few attributes for which data is extracted from datasets (e.g for Country with Labels and Codes) :

• Display Value : France
• Country Code : FR
• Numeric code : 56

In Create / User Request, we want to provide the "Display Value" - as SQL Enum gathered from above dataset,  to end users, and provision to target applications the Country Code and Numeric Code.

As the dataset may contain hundreds of lines, we do not want the target application connectors to include an unmanageable list of IF / ELSE conditions.

Is there an elegant way to :

• Provide the Display Value to end users without exposing the associated Codes in Create User Requests ?
• Store the identity Data accordingly to prevent from doing all computations in target app connector ?

Thanks a lot !

[sudeshjaiswal]

Hello @adriencosson,

If you are trying to consume the DATASET value in the CreateAccountJson, the currently you can only handle it via Dyanmic Attribute.

Thanks.

[adriencosson · Accepted solution]

Hi Sudesh,

That means there is now way to use it when providing birthright access if I'm right.

We found an alternative where, if a target application needs ID instead of Label stored in Saviynt, we can perform a first API call to get the ID from specific target app's table and retrieve the label, to put it in secondary call.