I dont getting configure LDAP on my netbox-chart #18265
Replies: 1 comment 1 reply
-
Aside: I can't help you with your helm chart, but I can show you how to stop your YAML getting mangled by github. Edit your post, and add three backticks ( Then in any case you need to describe the actual behaviour or problem you're seeing. Does helm reject your chart? Does Netbox deploy, but crash? Does Netbox deploy, but only let you login using local usernames and passwords? Are LDAP logins accepted, but the wrong groups assigned? Some other problem? Also, are you sure you really need both the LDAPBackend and RemoteUserBackend? RemoteUserBackend means that the front-end HTTP proxy is doing the authentication, and it seems unlikely that both would coexist nicely. I would suggest you use either LDAPBackend or RemoteUserBackend. |
Beta Was this translation helpful? Give feedback.
-
Hi guys, I dont getting to configure the LDAP on Netbox. I need help to understand what do to deploy the application. My code in values.yaml:
Can you help me to understand what to do? With these configs, when I try logon, shows the messages below:
"Errors
Please enter the correct username and password. Pay attention to upper and lower case letters."
In summary, I can deploy the application normally. However, I can only log in using the local admin user. When attempting to log in with LDAP (AD) users, the message above is displayed. I’ve already tried deploying with just the LDAP backend, but that didn’t work either.
I’m not sure if it makes any difference, but whether using one or two remote backends—with their respective configurations—in the application pod logs, there’s no indication of loading files from the
/etc/netbox/config/ldap/
directory, such asldap_config.py
, which I imagine should be loaded.Below is a snippet from the log that loads all files from the
/etc/netbox/config/
directory, except for theldap/
subdirectory:Beta Was this translation helpful? Give feedback.
All reactions