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 ?