Delimited source - entitlement transform?

I am configuring a delimited source in ISC. There are multiple entitlements for each user, separated by commas in a single cell ex: (Admin,Read-Only,Update), so ISC reads them as a single entitlement string. What do I need to do to split them into individual entitlements. I was hoping it could be accomplished via a transform vs a build map rule since I am unfamiliar with writing rules.

you can use split transform like this:

{
 "attributes": {
   "delimiter": ",",
   "input": {
     "attributes": {
       "attributeName": "entitlements",
       "sourceName": "HR Source"
     },
   }
 },
 "name": "Split Entitlements Transform",
 "type": "split"
}

if you want you can include account attribute type as well as given above if you need some filters

Hi @ianderso426

I understand your need for transform over rule. But the fact is using transform will affect the access. Meaning comma seperated access will be coming as one entitlement in the source which is not correct and this will overtime create issues in certification and new access provisioning..
Whereas with transform you will be displaying the access only rather than actually provisioning or de provisioning it. It will be displayed over identity attribute as what that iser holds. But under access section you will still see the entitlements from that delimited source as abc,xyz,vs… comma seperated

Now coming to buildmap rule. Its simple its a connector rule that you have to deploy to the tenant. You have to write a snippet that will convert a string into the list. thats all.
And then in whichever attribute you are storing mark that as multivalued attribute.

Thanks

1 Like

Hi @ianderso426

Another better solution could to process your csv file before importing into ISC.

you can just split one line per entitlement for each user.

For example:
If you have the csv file :

userid,groups
jdupont,"Admin,Read-Only,Update"

Output would be like :

userid,groups
jdupont,Admin
jdupont,Read-Only
jdupont,Update

This can be easly imported in ISC.

thank you, that makes sense as to why the transform wouldn’t work. Unfortunately, I’m brand new to ISC and unfamiliar with writing any kind of rules so I was hoping something like a transform would work since it can be built in the GUI.

If the CSV file is not containing a lot of records and you are doing this for testing only then you can follow the approach by @baoussounda in above post by simply making the changes in delimited file.

Whereas if this is a requirement then you will have to use the buildmap Rule for delimited files.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.