Domain filter policy set to OWN blocks totally the MUC component
I installed the latest 5.2.0-beta3 of Tigase Server with two Vhosts and defined in my init.properties:
As expected, users are limited to their own domains when they try to communicate with other domains.
But the MUC component became unreachable for all of my users on both of my domains.
I have been told that I should open a feature request for this issue, so here it is :)
#1 Updated by Artur Hefczyc over 4 years ago
- Assignee set to Artur Hefczyc
- Target version set to tigase-server-5.2.1
As a workaround I can suggest to give a list with user's own domain and the MUC component domain to the domain filter.
I think a proper solution would be to have yet another option such as OWN_SUBDOMAINS which would allow the user to communicate within own domain and all subdomains.
To be honest I am kind of surprised with the request as I thought nobody really uses this feature.
#3 Updated by Wojciech Kapcia over 4 years ago
- Status changed from New to Resolved
- Assignee changed from Wojciech Kapcia to Artur Hefczyc
As per --domain-filter-policy
OWN allows users to communicate with all other users on the same domain. Plus it allows users to communicate with subdomains such as muc.domain, pubsub.domain, etc...
I modified processing of
OWN policy instead of creating yet another one @OWN_SUBDOMAINS@.