https://github.com/lldap/lldap logo
Leg4cyV1per - Hi I’m currently setting up LLDAP...
# troubleshooting
l
Hi I’m currently setting up LLDAP for my nifi authentication. I am having issues because I am unable to talk to the secure ldap port 6360. Is there an external way to test the port? Both are running in docker containers with a network setup for them and a subnet specified due to nifi configurations
a
message has been deleted
n
You should be able to talk to the LDAPS port using the ldapsearch binary. Make sure you run it from where you want to test the connection (i.e. inside the nifi container)
l
When I attempt to do that I get the following message: ldap_sasl_bind(SIMPLE): can’t contact LDAP server (-1)
I am currently using self signed certificates as I am still busy testing in case that makes a difference
I used the following command
Copy code
ldapsearch -x -H ldaps://localhost:6360 -D "uid=admin,ou=people,dc=test,dc=local" -w adminPassword -b "ou=people,dc=test,dc=local" "(uid=admin)"
the following command does work however it is not ldaps and unfortunatly Nifi requires ldaps
Copy code
ldapsearch -x -H ldap://localhost:3890 -D "uid=admin,ou=people,dc=test,dc=local" -w adminPassword -b "ou=people,dc=test,dc=local" "(ui
d=admin)"
This is the message I get from lldap docker logs 2025-04-16T11:44:51.148826575+00:00 ERROR 🚨 [error]: [LDAPS] Service Error: while handling incoming messages: while receiving LDAP op: unexpected end of file
n
The error above usually means you sent an LDAP message to the LDAPS port
l
would this classify as a LDAP message?
Copy code
ldapsearch -x -H ldaps://localhost:6360 -D "uid=admin,ou=people,dc=test,dc=local" -w adminPassword -b "ou=people,dc=test,dc=local" "(uid=admin)"
n
That should be LDAPS
l
I have also tried this command
Copy code
ldapsearch -x -H ldaps://localhost:6360 -D "uid=admin,ou=people,dc=test,dc=local" -w adminPassword -b "ou=people,dc=test,dc=local" "(uid=admin)"
but no luck I get the same message in the console
Copy code
ldap_sasl_bind(SIMPLE): can’t contact LDAP server (-1)
and the same error in the logs
Copy code
ERROR    🚨 [error]: [LDAPS] Service Error: while handling incoming messages: while receiving LDAP op: unexpected end of file
could it be that I configured something wrong? here is my config file. I use persistent storage for the docker containers hence I change the configs in this file https://cdn.discordapp.com/attachments/1362021246375559350/1362039373196951622/lldap_config.toml?ex=6800f184&is=67ffa004&hm=55a524f5dd00af60488d782c42d905690f0cef0fe8b26d53759ad4ac0f30da83&
n
You can try ignoring the certificate with ldapsearch by setting LDAPTLS_REQCERT=never
Just a hint for next time: it's better to grab the config dump at the beginning of the logs when setting verbose=true, that way your passwords are automatically sanitized
l
Ignoring it worked thanks 🙂 now I just need to figure out what the issue is in Nifi configs 🙂
n
And you are sure that it's the config that LLDAP uses, taking the cli, config file and env variables into account
l
Ok perfect will remember for next time at the moment I just left it to default or simple values that will get replaced
Yes I am 100% certain
n
Can you open an issue to clarify the error message? I can wrap it in LLDAP to explain why this error commonly happens
l
On github?
n
Aha no, I don't doubt where your config is from! I just mean that if you use the dump from the logs, that avoids one more source of errors (forgot to take an env variable into account, for instance)
l
I have no env variables set 🙂
But thanks for the advise I will follow that for next time
n
Anyway, your config was not the issue 🙂
l
you have not by chance assisted someone with a ldap configuration for nifi because i have been quite stumped with it. I either get invalid credentials for the ldap or it just closes the ldap connection and the logs are not much help from nifi's side
n
It's the first time I hear of that service 😄
l
O ok all good 🙂
n
Lldap verbose logs for the request?
l
I would need to check and let you know