There is no default correlation mapping, so prior to the aggregation, you can map the account attribute with the identity attribute as per your requirement.
When you set up this connector, it provides the default Correlation of “Name = name” (see screenshot)
However the documentation states there is no default. Can this be clarified? Should the default be ignored?
Additionally, the first option in the table, “Sailpoint Username (uid)” does not show up in the IdentityAttribute list. “Name” and “Username” appear, but it is unclear which one of these should the “SailPoint Username (uid)” value.
I did test this with an Ambassador Tenant, and “Username = uid” did get all of the users in ISC.
Hi @gmilunich, ideally, there should not be default value as we have not done any changes from our side as of now and documentation is correct.
For existing sources, you can manually update it like you have already updated and that resolved the concern. Also, I would like to update you that we are doing a change for default correlation and once that is done, you will see the default option for all the newly created sources and documentation will be also updated as a part of that change. Thanks!
@dinesh_mishra This is what I see when I create a new ISC Governance Connector. It provides the Default of Name and name.
Ideally, I would expect to not have to enter any correlation configuration out of the box for this connector, since the ID of the original account should be read as a schema attribute of this connector, and linking them should be known by default. It could then be up to the administrator to change this if they wanted, but out of the box most people I have talked to about this have expected it to work OOTB (since it shows defaults), and have been confused as to why it isn’t.
Currently, it seems that to get everyone returned, Username = uid seems to be what works for this.
I look forward to seeing some of the changes.
