group-user association attribute changed after click on "count groups" #12682
Labels
Milestone
Comments
This comment has been minimized.
This comment has been minimized.
blizzz
added a commit
that referenced
this issue
May 17, 2019
* uniqueMember was the default so we did not know whether this setting is desired or the initial value * autodetection of the user-group association attribute runs only when it was not set (as far as we knew) * the default is now empty * thus LDAPProvider might return this value as well (in exceptional cases) * if a group base is given (edge case), use this instead of general base * resolves #12682 Signed-off-by: Arthur Schiwon <[email protected]>
1 task
nachoparker
pushed a commit
to nachoparker/server
that referenced
this issue
Jun 28, 2019
* uniqueMember was the default so we did not know whether this setting is desired or the initial value * autodetection of the user-group association attribute runs only when it was not set (as far as we knew) * the default is now empty * thus LDAPProvider might return this value as well (in exceptional cases) * if a group base is given (edge case), use this instead of general base * resolves nextcloud#12682 Signed-off-by: Arthur Schiwon <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the LDAP configuration, the user-group-association is set on uniqueMember (the default). Also available is "memberUid", which has downsides. Groups are checked and available.
After a while revisit the configuration. When you click on “Count Groups”, it kicks off the detection of the association attribute (when it is set to default, which happens to be uniqueMember). If the more or the same amount of users (→ sorting) are returned for both attributes, memberUid will be used instead of uniqueMember.
It should not change in this case.
From https://help.univention.com/t/nextcloud-13-group-sync-issues/10337
The text was updated successfully, but these errors were encountered: