Steph - Has anyone gotten LLDAP two work with t...
# troubleshooting
n
Let's see what you have so far
I dug a little bit, and without running any query with it I see an issue: when trying to extract the CN from the DN, it expects the DN to be formatted as
cn=username,...
but we return entries as
uid=username,...
, so it's going to fail to get the CN.
Instead they should request the
cn
attribute as part of the search request, and then in the response look for
cn
in the returned attributes
(bear in mind that I didn't look at the rest of the plugin, I just browsed the LDAP part)
f
ok thanks a lot, appreciated, ill have to parse what youre saying when im a bit less fried, here is an example of my env variables for the plugin
n
Basically, the plugin needs to be updated to work with LLDAP. They make assumptions about the response from the LDAP server that don't always hold. You probably need to create an issue with them
f
ok gotcha, thanks again for your help
s
@final_stephiroth would you mind giving an update here, with whatever you end up concluding? I have some loose plans of using sftpgo together with lldap as well
n
I'm also suspicious of the `cachedUserPasswords`: LLDAP doesn't respond with
userPassword
, and you intentionally cannot cache it. I feel like it'd require a re-design of the plugin
s
Looks like the cache can at least be disabled through another env var.
f
@sbj1576 i will pivot to OIDC and use LLDAP as a source of truth, I'll update you when I have something that works, could be a bit
s
Thanks, would love an update 👍