Uploaded image for project: 'Spark'
  1. Spark
  2. SPARK-1860

Implement group chat duplicate name deconfliction similar to 2.7.7

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.8.0, 2.8.1, 2.8.2
    • Fix Version/s: 2.8.3
    • Component/s: Group Chat
    • Labels:
      None
    • Environment:
      Any
    • Acceptance Test - Entry:
      Hide

      If a duplicate name exists in the room, Spark should either generate an appropriate nickname for the room or allow you to choose a nickname with a scope of the session. In any case you should be able to enter the room.

      Show
      If a duplicate name exists in the room, Spark should either generate an appropriate nickname for the room or allow you to choose a nickname with a scope of the session. In any case you should be able to enter the room.
    • Expected Effort:
      Unknown

      Description

      In Spark 2.7.7 when you joined a room and your name already existed, it would automatically assign you a serialized name and allow entry. In 2.8.x it will refuse entry and create a ghost user. If you attempt to join the room again it will join you to the ghost user, but the listed users in the room will be erratic. This was resolved in a nightly where the ghost user is no longer created, but you are still refused entry into the room. If your backing authentication system does not allow modification of your nickname, you have no way to enter the room without significant administrative effort.

        Attachments

          Activity

            People

            Assignee:
            guus Guus der Kinderen
            Reporter:
            tsoftware Leslie R. Thomas
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: