-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Oauth2 with linear.app is broken #259
Comments
Hi @NickeZ thanks for writing in 💯 Does this consistently happen? I might be out of my depth here but this error may indicate that the OAuth protocol may not be properly implemented (I have not tested this out yet) In short based on the OAuth2 protocol if the Authorization Request sent by Slack includes a Regardless this feels like a server side issue, I've inquired internally about this |
Yes, it has happened consistently over a couple of weeks while chatting with slack support.
This might be the case. I did try setting up a simple oauth2 integration using a rust app. Using that I had no problem authenticating.
The state parameter is correctly sent back and forth. I double checked the URLs and it doesn't change. The value of the state parameter set by slack is quite long. Maybe that contributes to some problem? Maybe the value is truncated by some proxy at slack?
I think the error message is quite vague and I have a hard time understanding exactly where the integration fails. |
Hi @NickeZ Where there OAuth flows with other providers on this workspace that where successful? Any chance you could join the Slack Community workspace in order to exchange your specific environment information and track down these logs? |
Hi @NickeZ would you be able to share what the provider configuration looks like? |
Hi, provider config:
slack manifest:
|
@NickeZ we've published a connector that successfully executes the hand-shack The linear provider config looks something like this {
"provider_type": "CUSTOM",
"options": {
"client_id": "xxxx",
"scope": [
"read",
"write",
"issues:create",
"comments:create"
],
"provider_name": "Linear",
"authorization_url": "https://linear.app/oauth/authorize",
"token_url": "https://api.linear.app/oauth/token",
"identity_config": {
"url": "https://api.linear.app/graphql",
"body": {
"query": "{ viewer { id email } }"
},
"http_method_type": "POST",
"headers": {
"Content-Type": "application/json"
},
"account_identifier": "$.data.viewer.email"
}
}
} Similar to your implementation, but it seems like |
Hello! I'm back on this task again. I updated all slack dependencies and now I get a bit further. When I do |
The slack connector that you have published works fine. But I need the customizability of running my own connector. |
I figured out the "state" problem. It is because I use firefox containers. It opened the first link as a "containerless" tab. But then when I pressed "Continue to linear" it opened a "Work" container. But the other issue still remains. I get a blank screen / 500. |
Hi @NickeZ thanks for getting back to us, Could you ensure that |
Yes,
|
@NickeZ thanks for sharing 💯 from what I can tell your configuration is nearly identical to the one used by the |
The
deno-slack
versionsDeno runtime version
OS info
Describe the bug
I'm trying to add linear.app oauth2 api to a slack app as an "external-auth". Whenever I try to authentiecate I get an error message "unable_to_parse_state", see attached image. I did double check that the state parameter has the same content before the redirect as after. Slack support told me to reach out here.
Steps to reproduce
Expected result
I expect the authentication to work
Actual result
Error message about parsing state
Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.
The text was updated successfully, but these errors were encountered: