-
Hello, my current LDAP config is: The error I get is server error 500 internal error, and the logs say: Using direct bind with the INVENTREE_LDAP_USER_DN_TEMPLATE option works, but that way I am forced to choose a DN template and not all users of the app have the same one. Also I could not get that option to work using the samaccountname, only with commonName Reproducing the same logic but with a ldap command line search tool (ldapvi), searching the same base DN, using the same binding DN, works as expected and I am able to search for users. Any thoughts? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
In case full trace helps: Loading config file : /home/inventree/data/config.yaml |
Beta Was this translation helpful? Give feedback.
-
Just had a meeting about this with our LDAP expert, and he's stumped as well. Any ideas, anyone? We might have to give up on this app if we cant get this to work. Thanks! |
Beta Was this translation helpful? Give feedback.
-
I have managed to fix this The new config: Adding the INVENTREE_LDAP_USER_DN_TEMPLATE option but leaving it empty did the trick. Not providing that info forces it to search in the Base DN. I think that by providing that info, you make the INVENTREE_LDAP_BASE_DN redundant, as it never felt the need to use it. This way, with the info left out, it searches the entire base as it should. |
Beta Was this translation helpful? Give feedback.
I have managed to fix this
The new config:
INVENTREE_LDAP_ENABLED=True
INVENTREE_LDAP_SERVER_URI=ldap://server
INVENTREE_LDAP_BASE_DN=DC=central,DC=corp,DC=com
INVENTREE_LDAP_START_TLS=False
INVENTREE_LDAP_DEBUG=True
INVENTREE_LDAP_USER_DN_TEMPLATE=
Adding the INVENTREE_LDAP_USER_DN_TEMPLATE option but leaving it empty did the trick. Not providing that info forces it to search in the Base DN. I think that by providing that info, you make the INVENTREE_LDAP_BASE_DN redundant, as it never felt the need to use it. This way, with the info left out, it searches the entire base as it should.
Honestly this seems more like a bug than a feature. I've never before encountered a config issue which i…