MUC Nick Sharing can cause rejoin to fail

Description

Suppose two clients, with resources A and B are both joined to a chatroom.

If B attempts to rejoin (ie, send a MUC join when already joined), the code first checks for a nick-share possibility by comparing the first listed MUCRole's bare jid with B's bare jid, which matches.

To check for rejoins, the code checks to see if the occupant has the same bare jid - if the first listed occupant is A, this fails, however the client is already joined, and so errors will occur later.

Environment

None

Activity

Show:
Fixed

Details

Assignee

Reporter

Fix versions

Priority

Created October 27, 2017 at 3:31 PM
Updated October 27, 2017 at 5:32 PM
Resolved October 27, 2017 at 5:32 PM

Flag notifications