para LDAP config is not picked up correctly
See original GitHub issueI’m setting up server like this:
scoold server
- application.conf
- para.security.ldap.server_url = "ldap://test.com"
- (...other)
para server
- application.conf
at first try, everything is working but after adjust some of the configuration. I am not sure what is the root cause. now suddenly there is an error cannot authenticate with LDAP server localhost:8389 (which is the default)
my workaround is:
I have to also put the config inside the para (application.conf) too and now it is working again.
scoold server
- application.conf
- para.security.ldap.server_url = "ldap://test.com"
- (...other)
para server
- application.conf
- para.security.ldap.server_url = "ldap://test.com"
- (...other)
Issue Analytics
- State:
- Created 5 years ago
- Comments:31 (20 by maintainers)
Top Results From Across the Web
How to Troubleshoot LDAP Authentication - Knowledge Base
The LDAP server is not reachable (check the service routes); User does not exist in LDAP server; Username and/or Password is wrong; Bind...
Read more >Troubleshooting LDAP server connections - Pexip Infinity Docs
Check the Pexip Infinity LDAP configuration settings (Users & Devices > Administrator authentication) to ensure that all objectClass and LDAP field names have ......
Read more >Jenkins LDAP Configuration Troubleshooting
LDAP groups are not recognized by Jenkins. In /whoAmI LDAP groups do not appear. I attempted to Configure the LDAP Plugin and I'm...
Read more >Troubleshoot LDAP Server Integration Errors - BeyondTrust
Most LDAP problems will result in a single Failed to Authenticate message when trying to log in. The best way to troubleshoot a...
Read more >Troubleshooting LDAP - GitLab Docs
GitLab does not cache or store credentials for LDAP users to provide ... If LDAP is set up correctly on this node, it...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m having a hard time configuring scoold for AD auth using the UPN. This one works for me:
As you probably guessed, this lets you in with
user.name
. But I want to log in with the full email address. So I tried withNone of them works. I’m afraid the
@
might not be escaped correctly somehwere. Any ideas?For the record, here’s everything LDAP-related:
@albogdano I apologize for being MIA for a couple days. I have tried that. That is when I start getting <ROOT> showing up in the network trace. I’m going to dig more into that as well as other ways to BIND (eg. full DN).