Good morning all, Has anyone been able to bind using LDAPS to his/her AD server using the AD plugin? We've updated to the latest version of the plugin, are using the forceLdaps system property, have imported the cert into the Java keystore on the Jenkins server, and know plain-text auth works.
As background, TLS does not seem to be an option for us, and we've been testing, mostly unsuccessfully, the LDAP plugin. We're using the matrix-based authorization, and successfully with only the AD plugin. With the LDAP plugin, though it seems we can bind in plain-text, we can't get sign-in to work, even in plain-text. However, when we imported the AD server's cert into the Java keystore on the Jenkins server, the LDAP plugin now seems to bind to ldaps://our.AD.server:636. The AD plugin didn't bind on port 636 prior to the cert import, and does not bind now. So, it seems the AD plugin provides authorization, but only insecure authentication; the LDAP plugin may provide secure authentication, but does not allow sign-in. We're not married to either plugin, just need one or the other to allow sign-in following secure authentication. Thanks in advance! -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
