j5v7c (j5v7c) asked a question.
Taking a survey, override master attributes or Okta expression language?
Hello, prior to Workday we populated the Okta manager field with the AD manager field, (ie Okta says manager is Fred Flintstone, AD says CN=Fred Flintstone,DC=AD,DC=COM). When Workday came along, we were unable to use the suggested mapping for manager (appuser.managerusername) because our implementation of Workday it is not an actual username, but the employeeID of the manager, so we created a custom field called managerUPN and mapped that over to AD to populate the manager field (working like a charm). The challenge is now I have an Okta base attribute with data in it (so very hard to clean that up). We tried mapping AD manager -> Okta manager as we had pre-workday, but the field inherited the profile master (workday) and is not currently updating the attribute for a workday mastered user, leaving me with incorrect data in Okta. I am taking a survey to see how others would solve the problem. Override the profile master (workday) with AD, or put in an Okta expression in the Workday -> Okta profile that pulls the AD data (getManagerUser("active_directory").displayName). Both end up getting the data from AD, I am struggling with which is the better of the two. Thoughts?
The issue seems to be related to the fact that you have multiple Profile Masters in your scenario and this scenario is best suited for Attribute Level Mastering. This is a feature from Okta that allows you to inherit certain attributes from certain Profile Masters as needed.
These details are outlined in our documentation at: https://support.okta.com/help/Documentation/Knowledge_Article/Attribute-Level-Mastering-1790609939 Should you have further questions on this with the specifics to your environment please open a support case with us and we will be more than glad to assist you.Thank you for choosing Okta!