Jenkins stops trying to authenticate to the real ldap server, i.e. sub-domain.domain.com, and starts trying to authenticate to domain.com

Article ID:224373827
1 minute readKnowledge base

Issue

  • Jenkins stops trying to authenticate to the "real" ldap server, i.e. sub-domain.domain.com, and starts trying to authenticate to domain.com

  • You get the stacktrace javax.naming.CommunicationException: domain.com:389

Environment

  • CloudBees Jenkins Enterprise

  • LDAP

Resolution

You need to specify the port:

<server>serv1.domain.com:PORT serv2.domain.com:PORT serv3.domain.com:PORT</server>
▼
This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.