Hi, I am facing an scenario where I read some attribute from HR, and use later for provisioning other sources. This is a personal id of the user, and goverment regulations does not allow systems to have it visible on screen.
As identity fields does not hide attributes, is there a workaround for this? I though to cipher the id value in an identity rule, and then decrypt on connector rules. But I would like to see your opinion, so perhaps I am missing a easier way.
My suggestion would be NOT to use such an attribute from HR. Find an alternative 
Yes it would be ideal, but it is used as a mandatory attribute for user creation in the systems connected to idn. They do not want to enter it manually, out from idn circuit.
Is it a Cloud based HR system or is it On Prem such as PeopleSoft?
If on-Prem I would think you should be able to hash it at least through a rule. But this again wouldn’t be recommended.
If they were to ask their legal counsel what they thought of the Idea, more than likely they would suggest finding a different unique identifier. The down-stream risk isn’t worth it in my opinion. Best to fix it now than to have to rearchitect it later.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.