Workday And ServiceNow Integration: OAuth Access or Refresh tokens are not available

[manish kale]

Hello Developers,
We are trying to integrate Workday and ServiceNow to get the users/workers' data from from workday and then map it into the ServiceNow user table using the REST API. We are trying to build the connection using OAuth 2.0. Consequently, we have configured the following things as listed below:
1. Credentials: Type - OAuth 2.0
2. Application Registration:

• Authorization URL- https://wd5.myworkday.com/{Tenant Name}/authorize
• Redirect URL - https://{Tenant Name}.service-now.com/oauth_redirect.do
• Token URL - https://wd5-services1.myworkday.com/ccx/oauth2/{Tenant Name}/token
• Default Grant Type: Authoriztion Code
• Send Credentials: In Request Body(Form URL Encoded)

3. OAuth Entity Profile: Grant Type - Authoriztion Code

So we have configured above things and when we view the credentials record we are getting the below error:

And if we click on the realted link "Get OAuth Token" we are redirected to a new page where we get the below error:

If anyone can let us know why we are getting these two errors please let us know. Your help will be much appreciated.

Best Regards,
Manish.

[manish kale]

Hello @ASHU_1 ,

It is the (Username and password) of ISU created in Workday = API Client Credentials.

[Kit Cheong]

During the ServiceNow "Get OAuth Token" process, when prompted to log into Workday use the ISU username and password.

Prior to this, when creating the Application Registry record in ServiceNow, use the client id/secret from the "API Client" section of Workday; not the "API Clients for Integrations". In my experience when using the "API Clients for Integrations" Workday does not perform the redirect during the "Get OAuth Token" process.

[manish kale]

Hello @Kit Cheong 

By following the given steps, we were able to log in to Workday after clicking on the link "Get OAuth Token". And we were also prompted with the dialog box to Eighter Allow or Deny. And even after clicking on the 'Allow button', the error message is still showing up as below:

Could you please let us know what could be going wrong?

[ASHU_1]

@manish kale We are also facing the same issue? were you able to move ahead? So, once the user name and password were provided, there was a small pop up - we selected allow, it then took us to a very basic looking page within Workday (not sure if this is where we have to reach) but back in the ServiceNow screen we got the same error message that you have? Did you find what went wrong and how to resolve?

Someone is saying it could be related to firewall? Some are asking to figure out a dataflow/threat model diagram, or the source/destination servers’ names. (Is this all really related? how to provide this information?)  

[manish kale]

Hello @ASHU_1 

Yes, Our issue was Resolved.
So there are different ways to register Client API in the Workday. So the workday team has to use the general method of Client API registration in the workday and also have to make sure that the workday team has added the Redirect URL from ServiceNow.
Once the above steps are done: the Workday team will provide the new Client ID and Client Secret. Update those in your ServiceNow Application Registry. 
And then try getting the Access Token Again from Credentials. - Log into the workday and the error will be gone. Access Token will be received. Hope that helps!