SailPoint ISC Google Workspace: locations & relations attributes not returning in aggregation

Identity Security Cloud (ISC) ISC Discussion and Questions
, , ,
1

I’m working with the SailPoint Identity Security Cloud (ISC) Google Workspace connector and ran into an issue with locations and relations attributes.

Account creation is working fine, and I can see both attributes being passed correctly in the provisioning plan. However, after running aggregation, these attributes are not getting pulled back into SailPoint.

Here’s what I’m currently sending:

relations

{"value":"Jon.Doe@test.abc.org","type":"manager"}

locations

[
  {
    "type":"desk",
    "area":"",
    "buildingId":"CA > RED > ROAD"
  }
]

My question:
Am I handling this correctly during account creation, or do these attributes need to be explicitly managed during account update operations for them to be picked up during aggregation?

Any guidance or pointers would be appreciated.

2

Hi @Sri_K - is this just happening for accounts created via SailPoint? Or all accounts for this source

3

Hi @robert-hails , Glad to reconnect.

It’s happening Only for the accounts created via SailPoint.

4

:waving_hand: yes likewise!

Are the locations/relations populated on the Google side? Can you see them in the Google Admin Console?

5

@robert-hails I’m unable to see the locations and relations attributes populated on the Google side, even though I’m passing the correct values

6

assuming same behavior with one location versus the array?

  {
    "type":"desk",
    "area":"",
    "buildingId":"CA > RED > ROAD"
  }
7

I’ve only tested by passing a single location object within an array. If I send it as a standalone object (not in an array), it results in a formatting error.

8

Are you using the VA based or SaaS based connector?

9

Saas Based connector