You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use circles with the collectives app, now I noticed after updating to 24.0.5 that some users can not see their collectives or shared files if they are members of a group which is the member of the circle.
E.g. our setup is similar to:
LDAP groups:
member
events
Collectives (= circles)
event team -> owner: user admin, members: group events
help -> owner: user admin, members: group member
An user who is member of member and events can only see shares of circles event team but not of help.
(This is a bit more complex as there are more circle <-> group mappings, and some work but some do not.)
I am not sure what information I can provide to track this down, it first appeared when updating to 24.0.5 from 24.0.3.
The text was updated successfully, but these errors were encountered:
The only difference between circles that work and the ones that do not work is that the API response says: initiator: null
for the not working ones.
Moreover I noticed that oc_circles_member is not in sync with the group members.
Meaning there are users missing added to a group (using LDAP) as well as deleted members still listed which were removed using occ user:delete.
susnux
changed the title
Member of groups are not handled properly
Group members not updated
Sep 27, 2022
We use circles with the collectives app, now I noticed after updating to 24.0.5 that some users can not see their collectives or shared files if they are members of a group which is the member of the circle.
E.g. our setup is similar to:
member
events
event team
-> owner: user admin, members: groupevents
help
-> owner: user admin, members: groupmember
An user who is member of
member
andevents
can only see shares of circlesevent team
but not ofhelp
.(This is a bit more complex as there are more circle <-> group mappings, and some work but some do not.)
I am not sure what information I can provide to track this down, it first appeared when updating to 24.0.5 from 24.0.3.
The text was updated successfully, but these errors were encountered: