https://github.com/lldap/lldap logo
Icon of Sin - Authentik LLDAP configuration
# troubleshooting
i
Authentik LLDAP configuration
Hello
n
Can you share the latest LDAP query? Just the first line is enough
i
DEBUG ┝━ 🐛 [debug]: | msg: LdapMsg { msgid: 50, op: BindRequest(LdapBindRequest { dn: "uid=lldap-authentik-bearer,ou=people,dc=example,dc=com", cred: LdapBindCred::Simple }), ctrl: [] }
lldap-authentik-bearer is just a user with lldap password and readonly groups
n
That's the login, we need the search request
i
okay my bad
first line is enough ?
Copy code
DEBUG    ┝━ :bug: [debug]:  | msg: LdapMsg { msgid: 51, op: SearchRequest(LdapSearchRequest { base: "", scope: Base, aliases: Always, sizelimit: 0, timelimit: 0, typesonly: false, filter: Present("objectClass"), attrs: ["altServer", "namingContexts", "supportedControl", "supportedExtension", "supportedFeatures", "supportedCapabilities", "supportedLdapVersion", "supportedSASLMechanisms", "vendorName", "vendorVersion", "subschemaSubentry", "*", "+", "+"] }), ctrl: [] }
n
Okay, that's the schema request 🙂 There should be a query with base DN ou=groups,dc=...
I expect it to have "member" in the requested attributes
i
i dumped it into a text editor
there is no member
i am trying to fnid the entry you wanted
n
And then in the list of returned groups, there should be the users
i
Copy code
DEBUG    ┝━ :bug: [debug]:  | response: SearchResultEntry(LdapSearchResultEntry { dn: "", attributes: [LdapPartialAttribute { atype: "objectClass", vals: ["top"] }, LdapPartialAttribute { atype: "vendorName", vals: ["LLDAP"] }, LdapPartialAttribute { atype: "vendorVersion", vals: ["lldap_0.6.1"] }, LdapPartialAttribute { atype: "supportedLDAPVersion", vals: ["3"] }, LdapPartialAttribute { atype: "supportedExtension", vals: ["1.3.6.1.4.1.4203.1.11.1"] }, LdapPartialAttribute { atype: "supportedControl", vals: [] }, LdapPartialAttribute { atype: "supportedFeatures", vals: ["1.3.6.1.4.1.4203.1.5.1"] }, LdapPartialAttribute { atype: "defaultNamingContext", vals: ["dc=example,dc=com"] }, LdapPartialAttribute { atype: "namingContexts", vals: ["dc=example,dc=com"] }, LdapPartialAttribute { atype: "isGlobalCatalogReady", vals: ["false"] }] })
sorry, this is probably not what you are lookng for
n
That's the root dse response
i
is it possible the sync is not syncing everything somehow ?
n
Maybe authentik caches stuff and doesn't request again?
i
yeah possibly
i believe so since the requests are getting shorter and shorter lol
any keywords I should look out for ?
n
Search request with a non empty base
dont know if it means something but
got it, I dont have any so far
I will check the older logs maybe there is smth there
n
Maybe reset authentik?
i
Actually I deleted the older connectoin I had and remade this one
so this one is new technically
I looked through 12 search requests, all of them have base : ""
is thats how its supposed to be
n
That's the root dse request
The "index.html" if you want, describes the server
i
I dumped the whole log and those are the only search requests that are
n
Well then, authentik is not requesting anything again
Maybe because the users/groups already exist? I don't know how it works
j
I don't use authentik myself, so I cannot help. But since I don't see it mentioned before, did you check the example config? https://github.com/lldap/lldap/blob/main/example_configs/authentik.md
i
yes, the example config has a part that is missing that is probably causing the issue
r
you found ? cause i got it syncing but not the groups members
@Icon of Sin
cause of that my groups are empty
filled it with random shit cause its required but
searched a bit and it should be uid or dn i guess ? but im not sure i tried
tried distinguishedName too idk
k i found to add to the exemple config x) Lookup using a user attribute turned off and User membership attribute to distinguishedName
n
That seems weird, I would expect it to be "memberOf" or "member"
r
Idk it works not gonna complain 😂
Memberof might have worked
But in the documentation of authentik it says if group is member put distinguishedName so i tried
n
Oh, I see
More LDAP inconsistent naming and confusing explanations
Yeah, I see what they mean in their docs
DN is correct
i
can confirm it works
merci
n
Can either of you send a PR to update the docs?
i
I dont have a github account unfortunately
n
@realspinelle can you take care of this?
r
Sure
@nitnelave done