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

[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":"test1@google.com","type":"other"}. In my provisioning policy, I can easily generate the required email address (e.g., test1@google.com) from identi…