Hi Chad, it was good seeing you at Empower. 

I think we're mainly stuck on the proper Host URL, and possibly where we should be including the "body" (client_id, client_secret, etc.).  See below.

1. Host URL - here is Workday's published path, and what is working in Postman where we are executing the Post command.  However, in Workflow, this returns a 400 Bad Request error when setting up the webservice. 
   1. https://wd2-impl-services1.workday.com/ccx/oauth2/[tenant]/token
   2. When we use our application user interface login URL, Test URL authenticates "successfully" returning a 200 level code, but the call to get token isn't successful, returning a "not in the right context" error from our Workday system.
      1. https://impl.workday.com/[tenant]/login.htmld?redirect=n
      2. Returns this in the httpformpost_content:

         1. httpformpost_content
            
            <?xml version="1.0" encoding="UTF-8"?>
            <wml:Application_Error xmlns:wml="http://www.workday.com/ns/model/1.0" Type="Server Error">
             <wml:Message>No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.</wml:Message>
            ...and 1 more. Double click to see all values.

2. Authentication
   1. We're using a system account for credentials (not default authentication)
3. Our URI seem correct based on the Workday documentation
   1. /oauth2/v1/token
4. Body
   1. Since we are still trying to just obtain an access token, there is no body per se.  
   2. We are currently putting the client_id, client_secret, grant_type, refresh_token in the Form Data section (see attached)
5. Tool
   1. We started using the HTTP Web Request without success, so we shifted to using the HTTP Form Post.  I wonder if that is also where we are having an issue.  What is the difference?