Change User inter-domain Communication Permission (Admin UI) (#476)

Activities

Eric Dziewa opened 10 years ago

Due Date
2015-09-29

Changed to Local domains. No feedback after submitting. Can still send across all domains.

Daniel Wisnewski commented 9 years ago

No change is made when submit is pressed. User is not given forbidden messages when relogged in and sends messages to blocked or modified domains.

Andrzej Wójcik (Tigase) commented 9 years ago

%wojtek - looks that it works correctly, as I got response with result. Could you check and confirm that this works fine?

wojciech.kapcia@tigase.net commented 9 years ago

(private note due to sensitive information)

Daniel, we test it for both NextPlane and Verizon and automated tests are passing, v:

Can you provide clear steps to reproduce the issue, including inter-domain communication setting?

wojciech.kapcia@tigase.net commented 9 years ago

Also - tried to reproduce the issue and couldn't:

Changed an old value: null (domains list: ) to a new value: LIST (domains list: atlantiscity) for user: tigase_1@atlantiscity

And after logging in as @tigase_1@atlantiscity@:

<iq type="set" id="ab86a">
<query xmlns="jabber:iq:roster">
<item jid="admin@firefly"/>
</query>
</iq>

<presence type="subscribe" to="admin@firefly">
<nick xmlns="http://jabber.org/protocol/nick">tig1</nick>
</presence>

<iq type="set" id="rsttig5" to="tigase_1@atlantiscity/Psi+/1">
<query xmlns="jabber:iq:roster" ver="61a07e34702bcb47d69d23eadf5cffb5">
<item subscription="none" name="admin" jid="admin@firefly"/>
</query>
</iq>

<iq type="result" id="rsttig5"/>

<iq type="result" id="ab86a" to="tigase_1@atlantiscity/Psi+/1"/>

<presence from="admin@firefly" type="error" to="tigase_1@atlantiscity">
<nick xmlns="http://jabber.org/protocol/nick">tig1</nick>
<error type="auth" code="403">
<forbidden xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/>
<text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" xml:lang="en">You can only communicate within selected list of domains.</text>
</error>
</presence>

Daniel Wisnewski commented 9 years ago

I can confirm this feature now works as intended, one thing of note:

Users currently logged in can still communicate to domains they are blocked from until they logout/login.

Type	Bug
Priority	Normal
Assignee	Daniel Wisnewski
RedmineID	3092
Spent time	3h

Child Issue

Parent Issue

#468

HTTP Admin UI

Issue Votes (0)

Watchers (0)

Reference

tigase/_server/server-core#476