After upgrade to 8.4p2 from 8.2p4, inactive attribute on identity is not updating based on IIQDisabled attribute of application account

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Which IIQ version are you inquiring about?

IdentityIQ 8.4p2 (Have upgraded from IdentityIQ 8.2p4)

We are running IdentityRefresh take with “Refresh Identity Attributes”.
There is an employee which has been terminated and hence the SuccessFactors account is disabled. After running aggregation and identityrefresh, the inactive attribute on identity is set to “true”
This is due to the mapping as follows:
“inactive” attribute of identity ------> “IIQDisabled” attribute of SuccessFactors application

Now the employee is rehired, so the SuccessFactors account is now active. We see the IIQDisabled value as “false”. However, the inactive attribute identity is still showing up as “true”.
Did anyone face any such issue. Or can anyone point me to what could be the reason for the same?
Thanks & Regards,
Milina Phalke

2

Hi,

I had the exact same issue a couple of weeks ago. It caused us quite some trouble! It indeed looks like IIQ’s behavior has changed since 8.4p2. After my discussion with SailPoint, they created an Engineering Tracking Number for this issue: IIQETN-12152.

The current workaround is to make the identity attribute non-temporary OR make it have a default value of false / true. We chose the first solution and it is now working flawlessly.

Can you please let me know if this solves it for you?

Regards,
Pieter.

3 Likes
3

@milinaphalke try with one option,

Use a global rule instead of mapping
In rule logic should be

Link sf = identity.getLink(context.getObjectByName(Application.class, "SF");
if (sf != null ) return sf.getIiqDisabled();
return false;
4

Thanks Pieter, yes have checked your post today. Will try out and update you.

5

Thanks Ranjan, we will check this and let you know.

1 Like
6

Thanks Pieter
We have changed the edit mode from “Temporary” to “ReadOnly” for inactive. And now the inactive attribute is getting updated as expected after running Identity Refresh task.
I understand the workaround was provided by SailPoint support team, but since this seems to be a bug, will a fix be provided for the same.
Do you have any idea on that?

Thanks & Regards,
Milina Phalke

1 Like
7

I think it is. It is registered under number IIQETN-12152.

If you want, you can give your feedback on this ETN via the ETN Future Product Placement Feedback Form:
https://app.smartsheet.com/b/form/7fb9f1dd17f349de9d6f4023d07d22d1

With that, you can at least notify SailPoint that you have the same issue.

8

Hi Pieter,

if it’s handy then pls provide more details or description of IIQETN-12152

that would be great.

Thanks,
Pravin

9

This is basically what I have…

1 Like
10

Hi Pieter,
Thank you!
I have marked the workaround suggested as solution.
I am also following with the support team regarding the engineering tracking number IIQETN-12152. Will keep you updated, if I get any update.
Thanks & Regards,
Milina Phalke