Uploaded image for project: 'HipChat'
  1. HipChat
  2. HCPUB-3432

User is not immediately kicked out of the room if removed via the API

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Low
    • Resolution: Fixed
    • Affects Version/s: HCS 2.2.4
    • Fix Version/s: HCS 2.4.0
    • Component/s: API and Integrations
    • Labels:
      None
    • Symptom Severity:
      Severity 3 - Minor

      Description

      This bug is very similar to HCPUB-3431

      Summary

      After removing a user from a private room via Remove member, the user is not immediately kicked out of the room. In some environments, it can take the room up to 5 minutes for the user to be kicked out.

      Environment

      HipChat Server 2.2.4
      HipChat Data Center 3.0.1

      Steps to Reproduce

      1. Login with a user to HipChat
      2. Add the user to a private room
      3. Join the room as the user that was just added
      4. Remove the user from the room by running:
        curl -XDELETE https://${FQDN}/v2/room/${ROOM_ID}/member/${USER_ID}?auth_token=${TOKEN}
        

      Expected Results

      User should be kicked out of the room right away or the room should disappear from the list as if the action was done in the client.

      Actual Results

      • The user will still have access to the room and see any new messages.
      • Any messages sent by the user will not be saved to the room history.
      • The user is still visible in people sidebar of the room for other room members.
      • Even if the user is kicked out of the room after a while, the user will still be visible as a member for other room participants.

      Notes

      It seems that the client periodically runs a refresh that updates the membership of the user in the client based on the the server values.

      Workaround

      The room list will be updated if you refresh the web client or logout/login of the desktop client.
      Otherwise, you should account for the delay when relying on this API endpoint.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              rberrelleza Ramiro Berrelleza
              Reporter:
              adridi Arbi Dridi
              Archiver:
              mandreacchio Michael Andreacchio

                Dates

                Created:
                Updated:
                Resolved:
                Archived: