Hi people. I am at a client which uses some user personal attribute in their application. As this is legated, this will not change, at least in the middle term. That is why we have to receive this value from HR, and propagate it to some of their applications.
Is there some way to mask this value in UI, with *** or some random value? Or some workaround?
Though I have never faced such an issue, one way I can think of is encrypting the values using Identity Attribute Rule and then decrypting in the Create Account Profile using the same key that was used for encryption. But org admins will have access to the rules and can easily decrypt the values if they wish to
Good point Nitesh! In this particular case we can ask HR to send it chipered, but as you say the rules for provisioning will have decryption key. Also, this attribute will function as anchor in some apps so it will be in correlation rules too.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.