<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z0000AH7wO8CQJOkta Classic EngineIntegrationsAnswered2024-10-31T22:08:39.000Z2024-10-24T21:12:41.000Z2024-10-31T22:08:39.000Z

StaceyS.22475 (Hyland Software, Inc.) asked a question.

Integration Issue with Workday

I'm working on integrating Workday and am having an issue determining the correct Application username format ad Okta username format combination to us so that Workday finds the Okta match and we can auto-activate users assigned to Workday.

 

Currently, our tenant is integrated with Active directory and uses the saMAccountName for the Okta username\login. Our saMAccount name is not populated from email or UPN or any other attribute. It is a custom ficticous name, that we refer to as the villain name. The Workday username is the employee ID.

 

 

After I completed all the Workday integration config, I set Workday as the primay (1) profile source and I set the following in Okta:

 

Under the Sign On tab, the SAML 2.0 settings - Credentials Details - selected Application username format 

Provisioning tab - To Okta (Workday to Okta) - General - selected Okta username format

 

But when I do a manual import, the Workday Profile can not find an Okta match. No matter what combination I try to use in the drop downs I mentioned above, it can't find a match.

 

Any suggestions?

 

 

 

 

 

 


StaceyS.22475 likes this.
  • Mihai N. (Okta, Inc.)

    Hi @StaceyS.22475 (Hyland Software, Inc.)​ , Thank you for reaching out to the Okta Community! 

     

    A matching attribute needs to exist in Workday as well as the Okta user profile for this to work. 

    You can look into the possibility of adding a custom attribute in the Okta user profile , but populating the value would imply manual input which is not scalable, or a potential import from an outside source for example Bulk Update Okta User Profiles via CSV Import

    If you have an account with the proper entitlement, I strongly recommend opening a case to work with one of Support colleagues to review your configuration, as setting Workday as a Primary Profile Source could override the Okta username, potentially impacting user login and downstream applications. 

     

     

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

     

    --

    Ask Us Anything about Workflows now thru 10/31

    Expand Post
    Selected as Best
  • Mihai N. (Okta, Inc.)

    Hi @StaceyS.22475 (Hyland Software, Inc.)​ , Thank you for reaching out to the Okta Community! 

     

    A matching attribute needs to exist in Workday as well as the Okta user profile for this to work. 

    You can look into the possibility of adding a custom attribute in the Okta user profile , but populating the value would imply manual input which is not scalable, or a potential import from an outside source for example Bulk Update Okta User Profiles via CSV Import

    If you have an account with the proper entitlement, I strongly recommend opening a case to work with one of Support colleagues to review your configuration, as setting Workday as a Primary Profile Source could override the Okta username, potentially impacting user login and downstream applications. 

     

     

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

     

    --

    Ask Us Anything about Workflows now thru 10/31

    Expand Post
    Selected as Best
    • StaceyS.22475 (Hyland Software, Inc.)

      "A matching attribute needs to exist in Workday as well as the Okta user profile for this to work."

      Can this matching attribute be the email address or does it have to be the username\login?

This question is closed.
Loading
Integration Issue with Workday