Spoke development - OAuth Token Via MID server issue

[Tim-S]

Hi,

I've created a spoke, based on the YAML representation of a REST endpoint.

Part of the process is creating / configuring the Connection Alias and associated connection/credential/oauth config etc. I believe this configuration is OK, but when I try and get a REST token (from the link on the credential record) I get this:

This is the configuration of the credential (yeah, I'll tidy the auto-generated name up!):

So the mid server is specified. This is the app registry record:

I've checked the outbound http log and can see the HTTP post to get the token:

As you can see the MID server is not specified in the request and there are no associated records in the ecc_queue.

I guess there's a configuration issue somewhere, any ideas would be appreciated, thanks!

[Tanushree Maiti]

Hi @Tim-S 

In Oauth profile update Authorization URL and Redirect url.'

Authorization URL is used to initiate the authentication process and obtain user consent

Redirect URL (or Callback URL) serves as the specific, pre-registered endpoint where the authorization server securely sends the user back with an authorization code.

Once done , test it and let me know what response code you are getting.

[Tim-S]

Hi Tanushree,

The Authorization URL is not required for Client Credential type grants, I don't think redirect is required either, if left empty it will auto-generate.

Thanks!

[Tanushree Maiti]

Hi @Tim-S 

1)In Outbound HTTP Requests  log, Search by url and check what response it is sending. 

Share the message. 

2)Also double validate end point.

3) Check whether Endpoint IP is blocked at your end or not.

• ping the oauth token url domain (ex: example.com )
• once you have the IP address, go to IP address access control.
• add the ip in the allowed list if it is not there
• Now try to get token.

Note: If possible using postman, you can test the integration once