|
Réda Housni Alaoui opened 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. |
|
As per [--domain-filter-policy](http://www.tigase.org/content/domain-filter-policy:)
I modified processing of |
|
Referenced from commit 11 months ago
|
|
|
Referenced from commit 11 months ago
|
| Type |
New Feature
|
| Priority |
Critical
|
| Assignee | |
| RedmineID |
1708
|
| Version |
tigase-server-7.0.0
|
| Spent time |
13h 30m
|
Issue Votes (0)
Watchers (0)
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 :)