Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Group members not updated #1166

Closed
susnux opened this issue Sep 26, 2022 · 2 comments
Closed

Group members not updated #1166

susnux opened this issue Sep 26, 2022 · 2 comments

Comments

@susnux
Copy link
Contributor

susnux commented Sep 26, 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:

  • 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.

@susnux
Copy link
Contributor Author

susnux commented Sep 27, 2022

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 susnux changed the title Member of groups are not handled properly Group members not updated Sep 27, 2022
@ghost ghost mentioned this issue Feb 7, 2023
@mejo-
Copy link
Member

mejo- commented Oct 24, 2023

Closing as duplicate of #1249 (because that issue has more discussion).

@mejo- mejo- closed this as not planned Won't fix, can't repro, duplicate, stale Oct 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants