Replies: 3 comments
-
I've tried adding the ldap read-only service account to the "is_active" ldap group which is the same group I'm using for AUTH_LDAP_REQUIRE_GROUP. Does the service account need to be in the same OU as the normal users by any chance? |
Beta Was this translation helpful? Give feedback.
-
Looks like you may be missing the ou for the netbox_bind user if it exists in one in your ldap. I assume it would also be
try adding ou to
Although I may be wrong as its not complaining about user not found or password wrong. |
Beta Was this translation helpful? Give feedback.
-
You're correct, the ldap read-only service account is not in the ou with all the other users and service accounts, it's at the root of the dit. As mentioned, this does not cause any problem elsewhere where the same service account is used as part of authenticating users. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey, so as far as I can tell (of course) I've got LDAP configured correctly, I know ldap is working as it's used to authenticate elsewhere without issues. It seems that django is complaining about a lack of privileges that the read-only account has but it's not telling anything more specific. I don't think it's complaining about a lack of access the user I'm trying to login with has because it's part of the netbox_admins group in ldap.
The django-ldap-debug.log:
The relevant section of ldap_config.py:
Let me know if you need the full dap_config.py
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions