RocketChat / RocketChat/Rocket.Chat

Unauthorized error when attempting to buy Zoom app

Open
#19,271 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feat: apps
Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

On a self-hosted instance of Rocket.Chat (latest docker develop), which is joined to rocket.chat cloud, with a payment method on file, attempting to purchase the Zoom app generates an "Unauthorized" error. There is no further data in the logs or the console.

Steps to reproduce:
  1. Run latest docker develop.
  2. Connect the instance to rocket.chat cloud services.
  3. Add a payment method to the cloud profile.
  4. Go to Marketplace and attempt to buy the Zoom app.
  5. You get an "Unauthorized" error.
Expected behavior:

Purchase and deployment of the Zoom app should be possible.

Actual behavior:

You get an "Unauthorized" error:

Zoom

Server Setup Information:
  • Version of Rocket.Chat Server: 3.8.0-develop
  • Operating System: Ubuntu 20.04.1 (docker)
  • Deployment Method: docker
  • Number of Running Instances: 1
  • DB Replicaset Oplog: Enabled
  • NodeJS Version: v12.18.4
  • MongoDB Version: 4.0.20
Client Setup Information
  • Desktop App or Browser Version: 3.0.3
  • Operating System: Windows 10 Version 2004
Additional context

No additional context.

Relevant logs:

No relevant logs.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the purchase flow on the listed Rocket.Chat Docker setup, after connecting it to Rocket.Chat Cloud and adding a payment method. Trace the Marketplace Zoom app purchase and deployment path, including where the Unauthorized response is surfaced; no files or tests are named in the issue. Done means the purchase and deployment complete without the Unauthorized error and a regression check covers the flow.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, typescript
Domain
backend, cloud, payments
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.