nextcloud / nextcloud/spreed

[BUG] Allow only one guest participant via email link

Open
#18,530 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: api 🛠️ feature: meetings 📅 feature: settings ⚙️
Dominant language
JavaScript
Stars
2.2k
Forks
586
Avg merge
18h 27m
Merged PRs (30d)
333

Description

[!TIP]

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Steps to reproduce

  1. Host a Talk "Webinar"
  2. Invite guest via email invite (a csv with one email)
  3. Open same link on two different private tabs
Expected behaviour

Nextcloud Talk should not allow the latter to join

Actual behaviour

Both people using the same link can join, while Talk reports only one participant

Talk app

Talk app version: 24.0.1

Custom Signaling server configured: 2.1.1~docker (Nextcloud AIO)
Custom TURN server configured: yes (Nextcloud AIO)

Custom STUN server configured: yes (Nextcloud AIO)

Browser

Microphone available: yes

Camera available: yes

Operating system: Any

Browser name: Any

Browser version: N/A

Browser log

N/A

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 issue in Nextcloud Talk 24.0.1 using the same email invite link in two private tabs, then trace the guest-link join flow and its interaction with the configured signaling server. Done means the second guest cannot join through the same link and Talk reports the correct participant count; add or update regression coverage where the join behavior is tested.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
audio-video-rtc
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.