Domain filter policy set to OWN blocks totally the MUC component (#280)

Domain filter policy set to OWN blocks totally the MUC component (#280)

Activities

	Réda Housni Alaoui opened 1 decade ago Hi everyone, I installed the latest 5.2.0-beta3 of Tigase Server with two Vhosts and defined in my init.properties: --domain-filter-policy=OWN 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 :)
	Artur Hefczyc commented 1 decade ago 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.
	wojciech.kapcia@tigase.net commented 1 decade ago As per [--domain-filter-policy](http://www.tigase.org/content/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@.
	Referenced from commit 1 year ago #280 -- Certificate Utils are innefective when using wildcarded certs https://projects.tigase.org/issues/280 bmalkow committed 1 decade ago c536d16e
	Referenced from commit 1 year ago #280 -- Certificate Utils are innefective when using wildcarded certs https://projects.tigase.org/issues/280 bmalkow committed 1 decade ago aa1f150b

Type	New Feature
Priority	Critical
Assignee	Artur Hefczyc
RedmineID	1708
Version	tigase-server-7.0.0
Spent time	13h 30m

Issue Votes (0)

Watchers (0)

Reference

tigase/_server/server-core#280

Please wait...

Page is in error, reload to recover