Or create a service group, and don't sync that group

Hello, anyone played with Netbox version 4.x running in docker to work with LLDAP ?

I assume you're aware of https://github.com/lldap/lldap/blob/main/example_configs%2Fnetbox.md ?

yes, but it seems this is not working anymore, was working on old version of Netbox; seems as some things have changed

and since I am running in docker stuff, most of the stuff is passed to Netbox (django app) via environment parameters

I don't have anything useful to add, just wanted to link to the documentation 🙂 If you figure it out, make sure to update it!

yeah, just wondering if anyone played already yet .. and figure it out

Hey! Thank you for the great work. I just want to let you know that

lldap:2025-07-06-debian

breaks this config for Radicale: https://github.com/lldap/lldap/blob/main/example_configs/radicale.md

Namely, I get an error

[ERROR] An exception occurred during PROPFIND request on '/': invalid attribute uid

when using

lldap:2025-07-06-debian

but

lldap/lldap:2025-05-19-debian

works perfectly fine.

Plugin config or native config?

Also, we didn't make any release in that timeframe, is Debian tracking nightly?

native config

Native is even more surprising, it doesn't list uid as an attribute, just as part of the filter

I'd be curious to see the verbose LLDAP logs for the failing version. Do you think you can get them and open a #992916353847668756 thread?

Done: https://discord.com/channels/898492935446876200/1391891649906610291

hey all! i recently started to use lldap in my network, but i am wondering if i am doing something wrong with bootstrap.sh. i am getting certificate error in password update. i use lldap container, and before i run bootstrap.sh, i am also updating ca-store of the container. it works perfectly fine, and bootstrap.sh adds everything except user password/groups. would it better to create a bug report regarding lldap_set_password, or is this a know upstream limitation.

Hi all, is this config still supposed to be working? https://github.com/lldap/lldap/blob/main/example_configs/authentik.md It seems that it's constantly bugging out about different attributes and not wanting to sync. If I setup "object uniqueness field" as "uid", then running ak ldap_sync slug I get "invalid attribute uid". If I change it to UUID, it seems to work if I sync only users and nothing else, but if I try to allow writeback or sync groups, then it just fails again, this time mentioning "invalid attribute distinguishedName" (Which I don't have setup anywhere)

If you're using nightly, it might have broken sure to a recent schema declaration

Before we didn't declare an LDAP schema and the tools just inferred it, but the latest version declares a somewhat incomplete (as we found out) schema, which the tools expect to be complete

For instance it's missing the uid attribute

There's a PR already addressing that, we're just making sure we don't break more expectations

But thanks for raising the issue!

Oh wow. I thought this was an issue with Authentik and I've nuked the whole thing after spending over a day on it :(

Sorry about that, it seems that you had bad timing... Try stable, it's more... Stable 🙂

Yeah, this one is on me, as I usually just containers without a tag. I've added the stable now. Another question if you might know - any way of deleting the default admin user?

Log in as a different admin and delete it

When I click delete, it remains there

Or if you're starting from scratch, you can configure a new name

Oh sorry, I didn't login as the other user

It's gone now, thanks :)