Zapier OAuth Connection Not Sending ClientID

Start date

Due date

Description

Summary

We have had a couple of customers reporting this, but after setting up a Zapier connection the URL is not sending the client_id. One customer is on 6.2.1, the second customer is a cloud customer so they are also on 6.

Observed Behavior

After setting up the Zapier connection and then trying to authorize with Mattermost, the client reports the error “OAuth Parameter Error: Invalid client id”

If you go into the developer console and search for document.referrer, the URL it is sending to Zapier looks like https://<server.url>/oauth/authorize?client_id=temp/... . The issue being that instead of the word temp it should contain the actual clientID you're trying to pass. If you copy that URL, replace temp with the actual clientId, then you can get the correct authorization screen.

QA Test Steps

None

Attachments

8

Activity

Show:

Michael KochellMay 27, 2022 at 7:45 PM

FYI the Zapier connector is now released publicly

Daniel SischyMay 27, 2022 at 7:43 PM

I’ve pushed 1.9.1 public. Let me know if you need anything else.

Michael KochellMay 27, 2022 at 6:42 AM

The beta version of the connector seems to be battle tested at this point (see comment here)

do you need me to push 1.9.1 public immediately? Or are you aiming for a specific date?

No specific date, but we want to ship it as soon as possible

Catalin TomaiMay 18, 2022 at 7:00 PM
Edited

Short answer, yes, since the current version is not usable. Unless Dylan needs/wants to do an extra validation cc:

Daniel SischyMay 18, 2022 at 6:56 PM

Just to confirm, do you need me to push 1.9.1 public immediately? Or are you aiming for a specific date?

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

Details

Assignee

Reporter

Checklist

Created February 1, 2022 at 4:16 PM
Updated February 25, 2025 at 4:04 PM