Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Connecting a Zapier account fails

Start date

Due date

Description

Original report: https://forum.mattermost.org/t/error-connecting-to-zapier/6410

Reproduced by JIRA reporter as well.

Steps to reproduce:
1. From the Mattermost System Console enable incoming webhooks, outgoing webhooks, custom slash commands, OAuth 2.0 service provider,
2. Then from the Integrations menu for my team, create a new OAuth 2.0 application for Zapier, following the directions at https://docs.mattermost.com/integrations/zapier.html#register-zapier-as-an-oauth-2-0-application, using callback URL https://zapier.com/dashboard/auth/oauth/return/MattermostDevAPI/
3. Next, at Zapier, create a new connected account for Mattermost, providing my Mattermost server URL with no trailing slash, the client ID and client secret copied from the Mattermost integration.
4. Click “Yes, continue,”

Observed: Error message from my mattermost server: “invalid_request: Supplied redirect_uri did not match registered callback_url”

Expected: Successful registration of the connected account.

QA Test Steps

None

Attachments

1

Activity

Show:

Jason BlaisJanuary 28, 2019 at 12:23 PM

Also confirmed by community member that this issue no longer reproduces.

Dylan HaussermannJanuary 4, 2019 at 2:37 PM

Tested this yesterday and was unable to reproduce the problem.

  • Tested with creating a new account and integration

  • Tested pre-existing account and integration

  • Tested connectivity and test posting to MM

No issues found.

Closing task.

Joram WilanderJanuary 3, 2019 at 3:21 PM

I was unable to reproduce locally on master or on ci-linux-mysql. Both worked as expected for me.

Linda MitchellDecember 28, 2018 at 3:37 AM

Testing notes: I also reproduced, on v5.7.0-rc1 (rctesting and Se server) and on v5.6.2 (ci-linux-mysql-prev). Zapier tests did pass successfully during 5.6.0 release testing.

Double-checked all settings, including past issues with trailing `/`s, trailing spaces in client ID and secret. Repro'ed on both `http://` and `https://` Mattermost servers.

Didn't find any obvious results trying to Google any possible recent changes on the Zapier side.

Cannot Reproduce
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

QA Assignee

Reporter

Fix versions

Sprint

Checklist

Created December 24, 2018 at 12:33 AM
Updated January 28, 2019 at 12:23 PM
Resolved January 3, 2019 at 3:21 PM