When this plugin is used on Windows, this field is null, and we use ADSI
and ADO through com4j to perform authentication.
OTOH, when this plugin runs on non-Windows, this field must be non-null,
and we'll use LDAP for authentication.
If non-null, Jenkins will try to connect at this server at the first priority, before falling back to
discovered DNS servers.
Active directory site (which specifies the physical concentration of the
servers), if any. If the value is non-null, we'll only contact servers in
On Windows, I'm assuming ADSI takes care of everything automatically.
If non-null, use this name and password to bind to LDAP to obtain the DN
of the user trying to login. This is unnecessary in a single-domain mode,
where we can just bind with the user name and password provided during
the login, but in a forest mode, without some known credential, we cannot
figure out which domain in the forest the user belongs to.
Selects the SSL strategy to follow on the TLS connections
Even if we are not using any of the TLS ports (3269/636) the plugin will try to establish a TLS channel
using startTLS. Because of this, we need to be able to specify the SSL strategy on the plugin
For the moment there are two possible values: trustAllCertificates and trustStore.
Copyright © 2016–2021. All rights reserved.