#435 Provide a more flexible way to configure who can create rooms
Reporter
kensuke.spb
Owner
MattJ
Created
Updated
Stars
★ (1)
Tags
mod_muc
Status-Fixed
Type-Enhancement
Milestone-0.11
kensuke.spb
on
Currently we can choose from restrict_room_creation = true / false / local.
I'd like to set it to local but also provide a way to allow another component (with JID like vk.domain.tld) create new rooms and invite users there. With "local", users at @domain.tld can create rooms, but not the transport at vk.domain.tld. Additional white list would be welcome.
The thing about vk.domain.tld is that it provides group chat feature and it needs to interact with mod_muc to translate those chats into XMPP world.
MattJ
on
Can you not just set it as an admin of the MUC service?
Component "conference.domain.tld" "muc"
admins = { "vk.domain.tld" }
Admins should be able to bypass all restrictions.
Changes
owner MattJ
kensuke.spb
on
Nope, it does not seem to work.
kensuke.spb
on
Ah, I missed that you places admins = under Component section, let me try again.
kensuke.spb
on
Yes, this way it works.
kensuke.spb
on
Sorry, I forgot to change the resctriction back to "local".
Finally, with "local" and admins set, the room is not created.
MattJ
on
Which version of Prosody?
kensuke.spb
on
Prosody 0.9.4.
kensuke.spb
on
Well, I added 12345@vk.domain.tld to admins where 12345 is my id in the social media (for which the transport is for). It works this way with "local" restriction mode, but this is not universal.
Is it possible to use wildcards?
Zash
on
Changes
titleProvide a more flexible way to configure who can create rooms
tagType-Enhancement
tagmod_muc
Zash
on
It should be very easy to write a plugin that hooks the 'muc-room-pre-create' and implements an arbitrary policy.
Currently we can choose from restrict_room_creation = true / false / local. I'd like to set it to local but also provide a way to allow another component (with JID like vk.domain.tld) create new rooms and invite users there. With "local", users at @domain.tld can create rooms, but not the transport at vk.domain.tld. Additional white list would be welcome. The thing about vk.domain.tld is that it provides group chat feature and it needs to interact with mod_muc to translate those chats into XMPP world.
Can you not just set it as an admin of the MUC service? Component "conference.domain.tld" "muc" admins = { "vk.domain.tld" } Admins should be able to bypass all restrictions.
ChangesNope, it does not seem to work.
Ah, I missed that you places admins = under Component section, let me try again.
Yes, this way it works.
Sorry, I forgot to change the resctriction back to "local". Finally, with "local" and admins set, the room is not created.
Which version of Prosody?
Prosody 0.9.4.
Well, I added 12345@vk.domain.tld to admins where 12345 is my id in the social media (for which the transport is for). It works this way with "local" restriction mode, but this is not universal. Is it possible to use wildcards?
It should be very easy to write a plugin that hooks the 'muc-room-pre-create' and implements an arbitrary policy.
Changes