Regarding Taking Manager value from different sources depending on a flag attribute

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

Hi,
We have implemented a transform on Manager attribute.
The transform checks a flag (attribute values in a lower priority identity profile authoritative source), and if the flag is Yes, then it takes manager id from the lower priority authoritative source if the flag is NO then it takes manager id from the higher priority identity profile’s authoritative source.

Manager correlation is same for both the authoritative sources and also we are sending exact same id of manager in case of flag yes or no.

We are seeing that manager value is not changing after flag is Yes, for other attributes, same logic is working fine.

Surprising thing is, in the preview, we are seeing that the new value is being populated, but no matter how many times we process the identities, the actual Manager value is not changing for the identity.

Any insights are appreciated.

Thank you,
Vaibhav

2

I have said this soooooooo many times.
You CANNOT add a transform to identity.Attribute.Manager at the profile level if it is populated at the source level.

I know that ‘technically’ you can add a transform, because it will physically let you, but it will NEVER populate it to the attribute, which is why it shows on the preview, and does not get passed through

Make a new attribute: manager.custom and use that for your transform

2 Likes
3

@phil_awlings
Okay, but if we were to change the manager value, how will we do it, we will still have to add identity attribute transform to take value from custom transform right ?

edit:
I think I got your point now,
Let me try this,
Use another custom identity attribute as Manager attribute…!!!

1 Like
4

@phil_awlings , it is working but how can I do the manager correlation,
Manager correlation will only be effective on the original Manager identity attribute.

Also, there are some attributes we are calculating which are manager’s email address and lifecyclestate, which depend on the referance transform and we use manager as a standard key to find these attributes..
could you please guide, you seem to have done this before..

5

Hi Vaibhav,

For what you’re describing, I think you’ll need to create a Manager Correlation cloud-executed rule here: Manager Correlation Rule | SailPoint Developer Community

The methods available are similar, but not identical to IIQ. You can access the javadocs here: Java Docs | SailPoint Developer Community

Thanks,
Margo

6

Good morning,
We made .custom attributes for each manager attribute that we required and referenced them instead. Not ideal, but functional.

We never explored using a cloud executed rule as that requires expert services hours