Software /
code /
prosody
File
spec/scansion/pep_pubsub_max.scs @ 12731:a314f5bff9f0
mod_muc: Better map restrict_room_creation to role permissions (behaviour change)
With this change and 427dd01f0864, room creation is now effectively restricted
to parent-host users by default. This is a better default than previous
Prosody versions (where room creation was not restricted).
The "local" option for restrict_room_creation is no longer used (any value
other than true/false won't change the default behaviour).
restrict_room_creation = true will grant prosody:admin the ability to create
rooms.
restrict_room_creation = false disables all permission checks.
Anything between these two can be achieved using custom roles and permissions.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Thu, 29 Sep 2022 12:30:52 +0100 |
parent | 11631:6641ca266d94 |
line wrap: on
line source
# PEP max_items=max [Client] Romeo jid: pep-test-maxitems@localhost password: password ----- Romeo connects Romeo sends: <iq type="set" id="pub"> <pubsub xmlns="http://jabber.org/protocol/pubsub"> <publish node="urn:xmpp:microblog:0"> <item> <entry xmlns='http://www.w3.org/2005/Atom'> <title>Hello</title> </entry> </item> </publish> <publish-options> <x xmlns="jabber:x:data" type="submit"> <field type="hidden" var="FORM_TYPE"> <value>http://jabber.org/protocol/pubsub#publish-options</value> </field> <field var="pubsub#persist_items"> <value>true</value> </field> <field var="pubsub#access_model"> <value>open</value> </field> <field var="pubsub#max_items"> <value>max</value> </field> </x> </publish-options> </pubsub> </iq> Romeo receives: <iq type="result" id="pub"> <pubsub xmlns="http://jabber.org/protocol/pubsub"> <publish node="urn:xmpp:microblog:0"> <item id="{scansion:any}"/> </publish> </pubsub> </iq>