MUC room nickname lock down and reserved nickname?

Matthew M
Added over 5 years ago

I wonder if Tigase supports nickname lockdown to enforce a unique or reserved nickname for each occupant. As in XEP 0045,

A MUC service MAY choose to "lock down" room nicknames

(e.g., hardcoding the room nickname to the bare JID of the occupant).

If so, the service MUST treat the locked nickname as a reserved room nickname

and MUST support the protocol specified in the

Discovering Reserved Room Nickname section of this document.

We would have to have an option for the server or some admin configure the room as non-anonymous, and lock the nickname exactly as what described above, e.g., enforce nickname=bare-JID for each member.

The questions are

  1. Does Tigase support this? This requires the support of "Discovering Reserved Room Nickname", which allows "User Requests Reserved Nickname" and server should respond with "Room Returns Nickname". See Examples 77 and 78 in

  2. If not, do you have any recommendation or tips for us to implement those? Which Java class would be a good start? We would also be happy to contribute back to your git repo, if you think it's a good idea to have this feature.

  3. Does the client has to support such nickname lock down? It looks so according to XEP:

Before attempting to enter the room,

a MUC-compliant client SHOULD first discover its reserved room nickname

(if any) by following the protocol defined in the

Discovering Reserved Room Nickname section of this document.

However, we are not quite sure if the majority of the clients would do so. Do you have any idea about this?

Thanks a lot for your help!