[OF-921] MUC Group ACLs are not updated when users join a group Created:
06/17/15 Updated: 11/27/15 Resolved: 10/19/15
Status:
Project:
Component/s:
Affects
Version/s:
Fix Version/s:
Resolved
Openfire
MUC
3.10.1
Type:
Reporter:
Resolution:
Labels:
Bug
Daryl Herzmann
Fixed
None
Ignite Forum
URL:
https://community.igniterealtime.org/message/249829
4.0.0
Priority:
Assignee:
Votes:
Major
Tom Evans
4
Description
Forum user reports that when a MUC room has a group ACL set, this group ACL does not get
modified when a user is added to a group. The user has to restart the server to get the ACL to
update properly.
Comments
Comment by Daryl Herzmann [ 07/01/15 ]
I attempted to reproduce this via the following procedure on 3.10.2
1.
2.
3.
4.
5.
6.
7.
Created users loser1 and loser2
Created group losergroup and added loser1 to the group
Created groupchat loserroom and verified that both loser1 and loser2 could access it
Changed loserroom to members only and set a member ACL for the losergroup
loser1 could join the room, loser2 could not
Added loser2 to losergroup
loser2 could now join the room
So I am not able to reproduce this issue, will ping the forums user again about this
Comment by Adam McKissock [ 07/26/15 ]
I'm having similar issues:
I'm using the Atlasssian Crowd authentication drivers, and I'm experiencing the following:
I have a room (testroom1), which is set to members-only and has a group (testgroup1) set as
room members.
I create a user (testuser1) and add that user to testgroup1 in crowd.
Once the group membership gets pulled through (i can see in openfire that the user is a member
of testgroup1) i login as that user and attempt to join testroom1. I get a "407: Registration
Required" error. If i restart the openfire server, the user can join the room. I've also found that if
i remove testgroup1 from the room's ACL and then re-add the group, the user will get an invite
to the room and be able to join.
I've tried leaving it quite a while between adding the user to the group and attempting to join,
and this results in the same issue. The issue is starting to become quite a headache for me, as
we're supposed to be migrating our 1500+ users to this new installation very soon.
Comment by Sascha [ 09/07/15 ]
I experience the exact same issue in my 3.10.2 environment. As a workaround I just remove
groups from a MUC's ACL and re-add it. This will kick everyone out of the room, but it will
work afterwards.
Comment by Tom Evans [ 10/15/15 ]
OK, confirmed this is a caching issue in the GroupAwareMap implementation. Investigating
options to clear the cache when a corresponding Group is updated; will report back shortly.
Comment by Tom Evans [ 10/16/15 ]
Submitted PR #311.
Comment by Tom Evans [ 10/19/15 ]
Currently evaluating additional discussion (via Github contribution) about removing secondary
caching entirely.
Comment by Tom Evans [ 10/19/15 ]
Updated secondary cache to manage group names only (rather than group instances) to enable
group retrieval from the primary cache, and also avoid creating orphaned groups. PR under
review.
Generated at Sun Mar 06 04:15:01 CST 2016 using JIRA 7.0.10#70120sha1:37e3d7a6fc4d580639533e7f7c232c925e554a6a.