We have 2 different sources and Identity profiles for Team members and contractors, All contractors managers are Team Members and they are in different source and Identity profile. I did manager correlation and tried unoptimized aggregation and still manager filed is not updating.
I see see manager DN under preview but not for Identity value.
From source we are getting manager as full DN, is there any configuration steps needed to populate manager name in the cube.
Hello @donavalli,
Apart from Manager Correlation Rule in the Authoratative Source, you also, need to make sure that “Manager” attribute in identity profile is also mapped. Then, and only then, the Managers will be populated as expected with Soft Link in the Identity Cube → Details Page.
Also, make sure that correct “Account Attribute” is mapped in the Manager Correlation Rule. As per your screenshots, it seems that you are using “Manager” Account Attribute, hence, I hope Manager account attribute is storing the Value as “Employee Number” of its Manager. As per your screenshot, The Manager Accounts Attribute is storing the DN of Manager. Hence, you have to perform below.
- Create a new Identity Attribute Named as “DN” in identity profile
- Map the Distinguished Name attribute from AD
- Go to Authz Source in Admin → Sources
- Go to Manager Correlation Rule section
- Change Employee Number with “Manager DN” identity attribute
- Save the changes
- Perform Unoptimized aggregation
- Validate the Data.
If all the above steps are correct, kindly run Single Identity Refresh and Check whether Manager Name is getting populated in Identity Cube → Details page.
Hi Ravi,
As per my knowledge, “Identity Value” will only come once you apply a refresh on the identity or do a full identity refresh. Until then it will come under “Preview Value” & because this is a (Manager) out of the box attribute you will see it as empty on the identity cube as well until it gets a valid manager identity Link.
Coming to Next part how can you map the manager so that it gets displayed on identity cube??
If you are getting the full manager form the source, then simply create a identity attribute dn (map that to AD DN attribute) and then make the DN attribute searchable using the VS Code Extension or by using API: put-identity-attribute | SailPoint Developer Community
Once you have that you can simply make the manager correlation as dn->manager in the source.
Hi Neeraj,
I am missing the attribute to make searchable.
Now if I go route what you said creating new attribute DN and make searchable then in source mapping if I map with DN–> manager and in identity profile under manager name I mapped contractor source with the manager then under identity cube I am seeing Contractor fullname instead of manager name.
Hi,
Please go through this Configuring Manager Correlation - SailPoint Identity Services
You have to map the DN attribute on Team members Identity profile. Because they are eventually your managers… ( So create a dn or your choice attribute amd map on the team members identity profile.)
and make dn attribute searchable.
Once that is done in Manager correlation your config would be dn->manager
And on contractor identity profile it would be (Manager → Manager attribute of source).
@donavalli to get any specific attribute of manager first you need to correlate the manager and apply that in the identity profile manager field. along with the correlation also make sure the uid of the user is same as the value which you pass
Secondly if you need any additional field of manager you need to use the below transform
thanks
Shantanu
Hi Neeraj,
In contractor Identity profile when I map manager filed with contractor source manager still it showing as contractor name under manager name in cube, if I change and map to Active Directory source manager field then I am seeing manager field in cube.
@donavalli , in all such multiple authoritative sources manager correlation cases, it is best to use the manager correlation rule. Its reliable and if the logic is right then definitely works when you do Unoptimized aggregation.
If you map tthe manager correlation on the authoritative source, then trying to map it again on the identity.Profile doesn’t work.
It will show on the preview, but will NEVER pass through to the cube
Hi Phil, I mapped in the source and under Identity Profile If I map AD source with manager then only I see manager in contractor cube, if I change to non employee source manager name it is not updating. Not sure if there is anything missing.
Not fully understanding the statement.
If you map the manager on the authorative source that who the manager will be.
If you want to use another source for the manager, or a variety of sources, un-map it in the authorative source and create a transform that you map on the identity profile,
or create a new identity.attribute ‘managerOther’ and use that for all downstream activities
We have 2 different source and Identity profile for Team members and contractors, all contractors manager are Team members, Our Contractor source is JDBC manager filed is DN value which is CN=xyz,OU=XXXX,DC=xyz,DC=Com. Now in Contractor source manager correlation is mapped with DN = Manager and in contractor Identity profile under manager mapped with contractor source manager filed then in identity cube manager is not updating, if I change manager filed from Contractor source to AD source and then I am seeing Manager is updating in contractor cube.