Wrokday Authentication issues

[Casey4]

When trying to setup Workday spoke using Oauth, after doing the registry, there is a step for Get Oauth token.

This opens up a workday UI screen instead of using the token to connect.

My understanding is this username/pw screen should not pop up because that would make it basic auth.

What could be the issue here? is the WorkDay setup not correct? or something missing in ServiceNow?

[MURALIR20469232]

Hello @Casey4 ,

Please find the below community links and let me know is you are still facing the issues.

https://www.servicenow.com/community/developer-forum/workday-and-servicenow-integration-oauth-access...

https://www.servicenow.com/community/servicenow-ai-platform-forum/oauth-2-0-connection-with-workday/...

*************************************************************************************************************
If my post is useful, please indicate its helpfulness by selecting " Helpful." This action benefits both the community and me.

If you like to share any information, please comment in this post so that it will be useful for our community.

Additionally, if you feel that any corrections are necessary in the content, please provide your feedback so that I can make the updates.

Regards
Murali.K.V.R

[Tanushree Maiti]

Hi @Casey4 

You need 

• Authorization URL
• Token URL
• Client id
• Client secret

With proper permission on the integration account (Client ID)

[Josh Pirozzi]

Hi @Casey4 ,

We are implementing this integration now and just went through this situation. What isn't covered / documented is that you need the Workday admin to provide both OAuth and Basic Auth Account Credentials.

What you're seeing is correct. You'll request the OAuth Token and then, in the logon pop-out, you need to provide the Basic Auth Credentials.

Hope this helps!

Josh

[Josh Pirozzi]

A couple of additional items:

• I believe the Roles were associated to the Basic Auth Credentials and the OAuth is only there to initiate the connection between ServiceNow and Workday.
• We're using the OOB Flow/Actions/Subflows for the integration and, when pulling data on Job Profiles, discovered there was a mapping issue. While the Job Profile Records were generating, at first only the Correlation ID came through. For the Job Profile Name and Code, ServiceNow was expecting a different header than what Workday provides. We updated the ServiceNow side to match what is coming through from Workday and fixed the mapping.