Follow up on custom LDAP attributes for NAbox managed harvest

[fast pier]

We're using a non-AD LDAP directory for our users, and I don't seem to find the ability to choose custom attributes for use in Grafana LDAP config. I found some older post here about a similar question (https://discord.com/channels/855068651522490400/1087202372616454164) , but was curious if there are any updates or changes to this ability in more recent NAbox releases?

I'm familiar enough with grafana configs that I could update it to what we need - however with the newer NAbox releases being container based I am unsure of the durability of any config changes, and also not even really sure how to perform those in the first place if we determine this path is suitable for our purpose.

[acoustic falcon]

Hello, please do your change in ldap.toml and send me what works, I’ll port that to the web ui

[fast pier]

It appears that all we need to be able to do for our specific case is to modify the username parameter in servers.attributes to uid: [servers.attributes] name = "givenName" surname = "sn" username = "uid" member_of = "memberOf" email = "email"

The rest of the default values seem correct, as the only field not populating in the Grafana LDAP auth test is the username.

The permissions defined in the NAbox LDAP config are also not applied to my test user on the Grafana auth test, but I am assuming that this is due to the fact that the username is not defined, and it can't look up any group memberships as a result.

[acoustic falcon]

You mean that doesn't work ?

Ah that's the Attributes part... I'm assuming search filter is correct

[fast pier]

yeah, correct. it seems that the search for the user works, but some later data is not populated based off it

in grafana LDAP test, all of these Redacted fields are correct and come from the LDAP directory, but the Username field is empty

[acoustic falcon]

Yes indeed, it’s takes statically from sAMAccountName, which is obviously wrong. Will be fixed in next release