Naga KishoreI.14293 (Customer) asked a question.
We are facing an issue where a custom OKTA User attribute (mastered from HR) is removed from user deactivation.
Description of the Issue:
We have created read only custom attribute in OKTA User (Default) profile and added mapping from the HR application. We observed that the attribute is being dropped after user is deactivated in HR ap0lication and OKTA. This attribute is needed when the user is rehired in SuccessFactors. As the attribute is dropped, we are facing issues in Rehire Process. Is there any explanation why the attribute is dropped after deactivation?
Note: There are some more read Only custom attributes mastered from HR which are not dropped from the user. Also, there is no other process or workflow removing the attribute in the above discussion
Hello @Naga KishoreI.14293 (Customer) , thank you for contacting Okta Community.
If you have two profile master applications, app1 and app2, and the user is unassigned from app1, they should retain the attributes on their Okta profile. When they are assigned to app2, that will update the attribute unless the attribute is not mapped from app2. So, when the profile master app is changed, the new profile master can override the attributes.
Regards.
--
Help others in the community by liking or hitting Select as Best if this response helped you.
Okta doesnt drop attributes on its own. Its very likely that the actual source data feed is the one dropping right before termination and therefore okta removes it..its also hard to say. it depends on the HR system you are using. im not as familiar with successfactors.