I think having a second user from the same browser join teh same pad silently disconnects the first

[JohnMcLear]

Feels like a regression, pretty sure this is my fault.

[ferrlen]

I think the issue is having the same user connecting to the same pad, regardless of whether they're in the same browser or not.

I have set REQUIRE_AUTHENTICATION: "true", maybe this plays a part? But now whenever the same authorID logs in, regardless of the name they set on Etherpad's interface, the previous session of that same user on that pad gets disconnected. Other users are still fine. It's as if Etherpad is trying to enforce having only one view per user, or transferring everything to the new socket.

In case it helps, these are some of my ENVs:

DB_TYPE: "postgres"
DISABLE_IP_LOGGING: "true"
AUTHENTICATION_METHOD: "apikey"
REQUIRE_AUTHENTICATION: "true"
# TRUST_PROXY is necessary for NGINX as reverse proxy:
TRUST_PROXY: "true"
SOCKETIO_ENABLED: "true"
# duration in miliseconds:
IMPORT_EXPORT_RATE_LIMIT_WINDOW: 10000
IMPORT_EXPORT_MAX_REQ_PER_IP: 1000
# Warning: more than the default 10 might lead to abuse. But this is required for ep_cursortrace to work.
COMMIT_RATE_LIMIT_POINTS: 1000
# Warning: 10MB might lead to abuse? Though TRUST_PROXY is true and it makes it easier to bypass this anyway
SOCKETIO_MAX_HTTP_BUFFER_SIZE: 10000000

[JohnMcLear]

Pr in to address this