[JIRA] (JENKINS-21073) Fix forceLdaps system property

fbelzunc@gmail.com (JIRA)

unread,

Mar 7, 2017, 7:26:02 PM3/7/17

to jenkinsc...@googlegroups.com

Félix Belzunce Arcos closed an issue as Fixed

Released since active-directory-1.34

Jenkins /

JENKINS-21073

Fix forceLdaps system property

Change By:	Félix Belzunce Arcos
Status:	Open Closed
Resolution:	Fixed

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

sebo.poczta@wp.pl (JIRA)

unread,

Feb 11, 2020, 2:34:04 AM2/11/20

to jenkinsc...@googlegroups.com

Sebastian Willdo reopened an issue

I seems that issue returns. I'm not able to connect with TLS to our AD. In logs(hudson.plugins.active_directory) i can see that plugin tries to connect with plain protocol ldap even after forcing ldpas in start parameters.

 
                                                                PATH=/opt/wii/test/csvn/bin:$PATH 
export JAVA_ARGS='-Dorg.eclipse.jetty.server.HttpConfiguration.requestHeaderSize=32768 -Dorg.eclipse.jetty.server.HttpConfiguration.responseHeaderSize=32768 -Dorg.eclipse.jetty.server.Request.maxFormContentSize=500000 -Dhudson.plugins.active_directory.ActiveDirectorySecurityRealm.forceLdaps=true -Djavax.net.ssl.trustStore=/opt/wii/java/jdk1.8.0_111/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Dhudson.footerURL=http://jenkins:8080' 
export JENKINS_JAVA_OPTIONS="${JAVA_ARGS}" 
source /home/jenkins/.bash_profile 2>&1 >/dev/null 
LOG_NAME=$(date +%d_%m_%Y).logs 
$JAVA_HOME/jre/bin/java -Xms4096m -Xmx4096m $JAVA_ARGS -jar $JENKINS_HOME/server/lib/jenkins.war --requestHeaderSize=32768 > $JENKINS_HOME/server/logs/$LOG_NAME 2>&1 & 
echo $LOG_NAME
exit 0
 
                                                            