Closed nagmat84 closed 1 month ago
Hi @nagmat84 - I'm unable to test this at the moment since I don't have an ldap server on-line at hand.
For this and #42475 can you:
Sorry, I forgot to put that into the report int the first place: Tested with Firefox 119.0.1 and Chrome 119.0.6045.123 on Gentoo Linux and Firefox 121.0 on Windows 11 (each with all extensions disabled).
The only suspicious message in the developer console (in Firefox and Chrome) is: Proxying an event bus of version 3.1.0 with 1.3.0 index.es.js:2337:14
. But I don't believe that this is bug related as this message appears on every Nextcloud page.
I guess I have found the underlying problem for this bug as well as #42475. It seems to be a permission-related problem.
I had promoted the LDAP group admins
to be the administrative group via php occ ldap:promote-group admins
. If I log in with an LDAP user which is in that group, the issue at hand as well as #42475 holds.
However, if I login with the original admin user admin
which has been created during the Nextcloud installation and which is member of the built-in group admin
(without plural-s), then the issue at hand as well as #42475 disappears.
I gave it a trial and also made one of my LDAP-admin users (tes03
in my case) a member of the built-in group admin
via php occ group:adduser admin 01976b91-c1e3-4fe2-9601-66e56ac766d3
. Now, php occ user:info 01976b91-c1e3-4fe2-9601-66e56ac766d3
looks like:
- user_id: 01976b91-c1e3-4fe2-9601-66e56ac766d3
- display_name: Testkonto 03 (test03@famna.de)
- email: test03@famna.de
- cloud_id: 01976b91-c1e3-4fe2-9601-66e56ac766d3@cloud.famna.de
- enabled: true
- groups:
- admin
- users
- admins
- quota: none
- storage:
- free: 2037256683520
- used: 0
- total: 2037256683520
- relative: 0
- quota: -3
- last_seen: 2023-12-24T13:50:51+00:00
- user_directory: /var/www/famna.de/nextcloud/data/01976b91-c1e3-4fe2-9601-66e56ac766d3
- backend: LDAP
Please note, that my user test03
is now member of admins
(the LDAP admin group) and admin
(the NC built-in group). After I logged out with test03
and logged in again, test03
the issues have vanished.
Apparently, promoting the LDAP group admins
to have admin privileges is not sufficient.
@nagmat84 So can this and #42475 be closed since they are duplicates of #42480 from what I understood?
This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions.
⚠️ This issue respects the following points: ⚠️
Bug description
I have set up LDAP User and Group Backend for users and groups. LDAP users, groups and group memberships seem to work, but when I navigate to "Settings -> Users" neither the groups are shown nor does the page list the group membership of the LDAP users.
Expected behavior: Settings -> User should properly show LDAP groups and group memberships for LDAP users Actual behavior: Settings -> Users only shows LDAP users, but neither shows LDAP groups nor group memberhips
When I press the button "Verify settings and count groups" during setup, Nextcloud correctly reports the number of groups. When I run
occ group:list
on the CLI,occ
correctly reports all LDAP groups.occ group:info
also works for an LDAP group. When I runocc:user:info <some LDAP UUID>
on the CLI,occ
correctly reports LDAP group memberships. When someone tries to share something (file/directory/calendar/other stuff) and starts typing the name of the entity to share with, auto-completion also includes LDAP groups. It is possible to share stuff with LDAP groups and access rights are granted to users as expected.Screenshot of the Settings -> User page (Note: Groups and group memberships are erroneously NOT shown):
Screenshot of CLI commands:
Screenshot of auto-completion during sharing (LDAP groups actually work and are found):
Steps to reproduce
Expected behavior
Groups and group memberships should be shown.
Installation method
Community Manual installation with Archive
Nextcloud Server version
28
Operating system
Other
PHP engine version
PHP 8.2
Web server
Apache (supported)
Database engine version
PostgreSQL
Is this bug present after an update or on a fresh install?
Fresh Nextcloud Server install
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response