LDAP realm failed to start

[maaliaz (Akbar)]

I have similar issue as before

Waiting for Elasticsearch to be up and running sonarqube-9.9.0.65466

Must-share information (formatted with Markdown): which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension) sonarqube-9.9.0.65466 how is SonarQube deployed: zip, Docker, Helm zip what are you trying to achieve what have you tried so far to achieve this Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)! sonar.log 2023.07.19 13:21:53 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /op…

Test connection using LDAP search is successful, but web.log has error “constructor threw exception; nested exception is org.sonar.auth.ldap.LdapException: LDAP realm failed to start: Unable to open LDAP connection”
ldapsearch -x -h IP -p 3268 -D “SonarQube@test.com” -W -b “dc=test,dc=com” cn

LDAP CONFIGURATION

sonar.security.realm=LDAP
sonar.authenticator.downcase=true
ldap.url=ldap://IP:3268
ldap.bindDn=CN=SonarQube,OU=OTHER,OU=SERVICES ACCOUNTS,OU=,DC=test,DC=com

ldap.bindPassword=
ldap.user.baseDn=DC=test,DC=com
ldap.user.realNameAttribute=cn
ldap.user.emailAttribute=mail

ldap.server1.followReferrals=false

[ganncamp (G Ann Campbell)]

Hi,

We’re not LDAP experts. Your best bet is to get a 3rd-party LDAP client to perfect your settings before you transfer them into your SonarQube configuration.

 
HTH,
Ann

[maaliaz (Akbar)]

The user was moved to a different Organizational Unit than the one originally configured. AD admin reverted the OU to its original setting, and SonarQube is now back to normal operations. Thank you for your quick reply.