I tried using the HTTP OAuth2 connector to connect to Slack so I can create use other Slack API endpoints which Workato doesn't support yet.
I am currently stuck at establishing the OAuth2 connection. After I click connect, and authorize the Workato connection in the pop up, the pop up displays "oops"
Can you share with me the link to the API documentation for the app you are trying to connect to as well?
K
Keith yau
said
over 7 years ago
It is a custom app for proof of concept, i can change whatever parameters or header. Is server failed to parse the url or there is limitation of code parameters?
Thanks,
CJ Wee
said
over 7 years ago
Can you send the screenshot of the Error pop up and copy past the URL of the pop up here? The url of this pop up will tell us what was sent back to Workato from your app.
*sorry, working at a cottage, reception is poor to upload a file
CJ Wee
said
over 7 years ago
Hi Keith,
It seems like it is a limitation with the code parameters as the URL contains the code. The response is probably not in a format that the HTTP connector is able to accept.
K
Keith yau
said
over 7 years ago
do you mean "POST" should be used instead of "GET" ? What parameters does "https://www.workato.com/oauth/callback" expect? Based on OAuth2, code and state should be good enough.
E
Ee Shan Sim
said
over 7 years ago
Hi Keith,
There could be a number of reasons why you are having this issue. Typically, when the redirect is received, the Workato framework immediately executes the token request. If that fails, you will see that error page.
I would like to understand the format of the expected token API request better from you. It is very likely an issue with differing request format. The default OAuth2 flow follows RFC 6749.
Shall we jump on a call together to look through this?
Saul Macht
HTTP OAuth2 for Slack
I tried using the HTTP OAuth2 connector to connect to Slack so I can create use other Slack API endpoints which Workato doesn't support yet.
I am currently stuck at establishing the OAuth2 connection. After I click connect, and authorize the Workato connection in the pop up, the pop up displays "oops"
Hi Saul,
The issue is with your OAuth2 Token URL. Based on Slack's API documentation, you need to use https://slack.com/api/oauth.access as the token URL instead.
CJ Wee
Hi Saul,
The issue is with your OAuth2 Token URL. Based on Slack's API documentation, you need to use https://slack.com/api/oauth.access as the token URL instead.
Keith yau
1. browser redirect to to myApp authoriz_url
2. authorize redirect to
https://www.workato.com/oauth/callback?code=XXXXXXXXXXX&state=nnnnnnnnnnnnn
3. https://www.workato.com/oauth/callback display same server error instead redirect to myApp token url with code , client_id, etc....
CJ Wee
Hi Keith,
Do you mind sharing with me what you have used for your Auth URL and token URL?
Keith yau
Hi there,
Here the are,
authorization_url: ->() {
'https://services-alexa.smartsimple.biz/Alexa/authorize.jsp'
},
token_url: ->() {
'https://services-alexa.smartsimple.biz/Alexa/access.jsp'
},
Regards,
Keith
CJ Wee
Hi Keith,
Can you share with me the link to the API documentation for the app you are trying to connect to as well?
Keith yau
CJ Wee
Can you send the screenshot of the Error pop up and copy past the URL of the pop up here? The url of this pop up will tell us what was sent back to Workato from your app.
Keith yau
https://www.workato.com/oauth/callback?code=64CCE8013D38ABD8C4C7AB5871F68F33&state=150220
*sorry, working at a cottage, reception is poor to upload a file
CJ Wee
Hi Keith,
It seems like it is a limitation with the code parameters as the URL contains the code. The response is probably not in a format that the HTTP connector is able to accept.
Keith yau
Ee Shan Sim
Hi Keith,
There could be a number of reasons why you are having this issue. Typically, when the redirect is received, the Workato framework immediately executes the token request. If that fails, you will see that error page.
I would like to understand the format of the expected token API request better from you. It is very likely an issue with differing request format. The default OAuth2 flow follows RFC 6749.
Shall we jump on a call together to look through this?
Regards,
Ee Shan
Product Manager, Workato
The new leader in Integration | Modern. Powerful. DIY.
Ee Shan Sim
FYI default token request format:
URL: "token URL provided"
method: POST
payload:
{
“client_id”: “abc”
“client_secret”: “123”,
“grant_type”: “refresh_token”,
“code”: “auth_code_received”,
“redirect_uri”: “redirect_uri”
}