ISC: How to split an account attribute to make it multivalued

[GilbertoOledo14 (Gilberto Oledo)]

Hello everyone!

We are using the NERM connector which we know to be a Web Services connector; we have an attribute of type “value1, value 2, value 3, value 4, value N…”

Is there any way to transform that value from being a string to a multivalued attribute during account aggregation?

Thanks in advance,
Greetings!

[sidharth_tarlapally (TARLAPALLY SIDHARTH)]

Hi @GilbertoOledo14

Can we map the Attribute in Account Schema ?

[GilbertoOledo14 (Gilberto Oledo)]

Hi, @sidharth_tarlapally

Thank you for replying.

Yes, I have marked it as multivalued but I can’t get it to split the values.

[sidharth_tarlapally (TARLAPALLY SIDHARTH)]

@GilbertoOledo14

Are we using a NERM direct connector or a web service?

[GilbertoOledo14 (Gilberto Oledo)]

@sidharth_tarlapally

We are using the NERM OOTB connector: SailPoint Non-Employee Risk Management
and in NERM this attribute is of type “ProfileSearch”.

[vbdm (Veera bhamidipati)]

Hi @GilbertoOledo14

If you have not seen already, please see these posts:

WebService connector does not aggregate multi valued attributes on 2nd call

Hi all, We are trying to add entitlements and accounts in a WebService connector. The JSON response is as follows for our secondary account aggregation call: [ { "name": "jira-software-users", "groupId": "11eed5b9-d6bd-45de-a992-7e5f7d65a1c8", }, { "name": "jira-users", "groupId": "59c5a0a4-be3a-4520-afe5-de5d9cae34d9", }, { "name": "atlassian-addons-admin", "groupId": "25c3f0fc-b6e5-4767-a459-2394daeb4554", } ] The pro…

Web Services Source | Multi-Valued Attribute Aggregation Issue

Hi Team, Greetings of the Day! We have configured a web services source on IDN. Below are the schema attributes that we have marked as entitlements: role_id (Single Valued) Role (Single Valued) TeamCode (Multi Valued) Multiple values that are present in “TeamCode” for each user is not reflecting on the UI even though the “TeamCode” attribute is marked as multi valued in IDN. When we try the same API call from POSTMAN, we can see that the response has multiple values for it as expected. If…

How to Provision Complex and Multi-valued Attributes on Google Workspace

Hi Community, I’m working with the Google Workspace connector in Identity Security Cloud and have a couple of questions regarding how to correctly format attributes during provisioning, specifically for the “Create Account” operation. Complex Attributes (e.g., Emails): Google Workspace expects email attributes in a complex format, like {"address":"[email protected]","type":"other"}. In my provisioning policy, I can easily generate the required email address (e.g., [email protected]) from identi…

[sidharth_tarlapally (TARLAPALLY SIDHARTH)]

@GilbertoOledo14

Do we have a chance to change the type of the attribute to ProfileSelect ?
As Profile Search is a String value and Profile Select is A List (Multivalued)

[GilbertoOledo14 (Gilberto Oledo)]

Hi, @vbdm

Thank you for your response.
I have checked and I think a good idea is to use a rule, however, I am not sure if I can add these rules to the “Non-Employee Risk Management” type connector.

[GilbertoOledo14 (Gilberto Oledo)]

@sidharth_tarlapally

I changed the attribute type, however, no change in ISC, it is still a text string.
I think the “problem” is the NERM API when getting the profiles, it returns a text string and not multivalued attributes.

I am thinking about using an after operation rule, however, I don’t know if this rule can be used in this connector.

[sidharth_tarlapally (TARLAPALLY SIDHARTH)]

@GilbertoOledo14

We don’t have connector rules for NERM
umm … may be utilise a web service connector and achieve this ?

[kanusha9 (Anusha Nallagrola)]

To convert the attribute (like “value1, value2, value3”) into a multivalued list, use the split transform during schema configuration or attribute transform mapping.

[GilbertoOledo14 (Gilberto Oledo)]

Hi, @sidharth_tarlapally

Yes, we can change the connector, it was not what we expected but to meet this use case, I think it is possible.

[GilbertoOledo14 (Gilberto Oledo)]

Hi, @kanusha9

Thank you for your answer

Do you have any example of this transform?
Thanks in advance.

[pattabhi (Pattabhi Nandarapu)]

Hi @GilbertoOledo14

When you say splitting multi values means: expecting values like below?

sending email each value with double quote.

{
  "attributes": {
    "sourceId": "source_id_value",
    "empID": "143",
    "userID": "bye",
    "email": [
      "[email protected]","[email protected]","[email protected]"
    ]
  }
}

UI display:

[GilbertoOledo14 (Gilberto Oledo)]

Hi, @pattabhi

Exactly what you have in your second image is what I want to get, that screenshot is of an account attribute, right?

I want to achieve that, since right now my attribute looks like this:

I am using the NERM connector and when I query my account information in NERM from the NERM API the attribute looks like this:

Do you know if there is a way to take that attribute as input and convert it to multivalue as in your image?

Or even, do you know if there is a way to convert it to multivalued when passing it as an attribute in the creation of another account?; since NERM works for us as an Authoritative Source to create identities

I hope I have explained,
Thanks in advance.

[pattabhi (Pattabhi Nandarapu)]

Hi @GilbertoOledo14

Yes, this is the JSON format for account creation from the REST API.

Reference from the topic: Create account API | Delimited source | multi valued attribute - #4 by pattabhi

Here, you can observe that this scenario is possible from the API alone, but not from aggregation, because each value needs to be surrounded by double quotes.

"[email protected]","[email protected]","[email protected]"

If you mention it in the source file, it will not accept multiple values. Therefore, it is only possible via the API call.

[pattabhi (Pattabhi Nandarapu)]

Hi @GilbertoOledo14

You can format the JSON input data from API as shown below.
"pm360_comercio_affiliation_ne_attribute": "8043392","9585781","9301628","8412073","8297974","9418813","8507388","9203646","8825224","8753958","8343792","8980031","8636750","9401198","8825690","8516388","8960189","9062075","9180735","7876996","7397628","9172519","9319230","9063860","9412102","8866749","7862944","7825416","8808853","8864909","7881216","7921933","9492995","9571481","9301690","9502661","9085161","743690","8955877","9022717","8962732","9272271","9220387","9419587","9146806","9493806","8762316","8030633","9283370","9374306"

[GilbertoOledo14 (Gilberto Oledo)]

Hi, @pattabhi
Thanks for the reply; I think I got it right, I just want to confirm.
OOTB, it is not possible during aggregation to become multivalue since it has to go in quotes for each value (something that does not happen today in my account).
The only way would be to format the json input as in your example; would this have to be outside of ISC, or is there a way for ISC to do it?

Thanks in advance,
Greetings!

[pattabhi (Pattabhi Nandarapu)]

As far as I can see, there is no OOTB. Let me see if I can find an easy way through a patch/put API call.

Thanks,
Pattabhi