#1451 MUC nickname registration is advertised on bare domain JID but only works on room JID
Reporter
Zash
Owner
Zash
Created
Updated
Stars
★ (1)
Tags
Compliance
Status-Fixed
Milestone-0.11
Type-Defect
Priority-Medium
Zash
on
Registration is done with the room JID per https://xmpp.org/extensions/xep-0045.html#register
However there is no mention of how this is to be advertised.
(Context: ejabberd offers registration on the bare domain)
21:41:29 MattJ> Registering on the room makes more sense to me than registering on a service
21:46:54 Zash> Either way, it makes sense to advertise the capability on the JID where you send the registration request, which makes it weird to advertise on the bare domain.
21:47:02 MattJ> Agreed
Prosody as of 0.11.{0..3} advertises the registration feature on both the bare host JID and on room JIDs:
https://hg.prosody.im/trunk/file/0.11.3/plugins/muc/register.lib.lua#l51
A common and sensible pattern in XMPP is that a feature is advertised on the JID where the service is available. Therefore Prosody should not advertise the registration feature on the host JID.
Registration is done with the room JID per https://xmpp.org/extensions/xep-0045.html#register However there is no mention of how this is to be advertised. (Context: ejabberd offers registration on the bare domain) 21:41:29 MattJ> Registering on the room makes more sense to me than registering on a service 21:46:54 Zash> Either way, it makes sense to advertise the capability on the JID where you send the registration request, which makes it weird to advertise on the bare domain. 21:47:02 MattJ> Agreed Prosody as of 0.11.{0..3} advertises the registration feature on both the bare host JID and on room JIDs: https://hg.prosody.im/trunk/file/0.11.3/plugins/muc/register.lib.lua#l51 A common and sensible pattern in XMPP is that a feature is advertised on the JID where the service is available. Therefore Prosody should not advertise the registration feature on the host JID.
Fixed in https://hg.prosody.im/trunk/rev/4e406944ff85
Changes