mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 08:15:52 +03:00
[GH-ISSUE #1171] [INTEGRATION] Troubles with connecting LLDAP to Peerube #418
Labels
No labels
backend
blocked
bug
cleanup
dependencies
docker
documentation
duplicate
enhancement
enhancement
frontend
github_actions
good first issue
help wanted
help wanted
integration
invalid
ldap
pull-request
question
rust
rust
tests
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lldap-lldap#418
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ChibyX on GitHub (May 10, 2025).
Original GitHub issue: https://github.com/lldap/lldap/issues/1171
Checklist
Description of the service
Peertube is a federated video hosting service. It has official LDAP plugin (https://framagit.org/framasoft/peertube/official-plugins/-/tree/master/peertube-plugin-auth-ldap). Unfortunately, it seems to lack configuration guides (the only mention of it in official docks is https://docs.joinpeertube.org/admin/managing-users#external-auths-support)
What you've tried
I based my config on the one I used for Nextcloud and Jellyfin:
What's not working
From Peertube's side:
From LLDAP's side:
Seems that LLDAP hears request from Peertube, but doesn't accept it, although credentials of bind user and user who performs login are correct.
@ChibyX commented on GitHub (May 10, 2025):
Meanwhile, after I switched Bind DN to admin with correct password, it now gives different messages on login attempts:
-/ on LLDAP side
-/ on Peertube side
@nitnelave commented on GitHub (May 10, 2025):
I didn't have time to investigate properly, but I do see from the logs that your peertube bind user is not privileged (not part of an admin/read-only group), so it can only see itself.
@nitnelave commented on GitHub (May 10, 2025):
And for the logs with the admin user, can you enable verbose mode and retry? I don't see the details on LLDAP side
@ChibyX commented on GitHub (May 10, 2025):
Oh, thanks, I thought, this was verbose mode. Now I enabled it properly, and it gives:
@nitnelave commented on GitHub (May 11, 2025):
I see what's wrong: your search filter is supposed to have the username inside (something like "(uid={0})" or some equivalent placeholder). Right now the query works, but returns more users than expected (all the peertube users).
You can also go back to using your bind user, if you add it to the lldap_strict_readonly group
@ChibyX commented on GitHub (May 12, 2025):
Well, I set Search filter to (|(mail={{username}})(uid={{username}})), as it was by plugin's default. I also had to bind groups for admin, moderator and user role because it turned to be mandatory (
info[12.05.2025, 10:49:34] Do not login user fchib because admin did not configure LDAP Groups.) After that I finally managed to log in. But now Peertube cannot recognize LDAP groups I belong to: without No group matched login set to true it doesn't let me in (warn[12.05.2025, 10:52:10] User fchib does not have any allowed LDAP groups.). And with this settings it doesn't give me admin role despite I belong tolldap-admingroup.Here's my entire group config:
Here's also LLDAP log entry on succesful login:
@nitnelave commented on GitHub (May 12, 2025):
For the "user group DN" (and the other ones) you put a search filter instead of a DN. A DN is just "uid=...,ou=..."
@ChibyX commented on GitHub (May 12, 2025):
Thanks! Now it works as expected, except for users who are members of
peertube_modsget administrator role instead of moderator. Anyways, for my instance it's not a big deal. I'll add example config to this repo soon.