From 33a07f8aa31d23f1f5b1172bc6583a90ca4cc370 Mon Sep 17 00:00:00 2001 From: Stephen Connolly Date: Fri, 25 Oct 2013 11:13:47 +0100 Subject: [PATCH] [FIXED JENKINS-16443] Document how to specify multiple servers for failover support - The code has supported multiple redundant servers, but the help did not indicate the support --- .../hudson/security/LDAPSecurityRealm/config.jelly | 2 +- src/main/webapp/help-server.html | 13 +++++++++++++ 2 files changed, 14 insertions(+), 1 deletion(-) create mode 100644 src/main/webapp/help-server.html diff --git a/src/main/resources/hudson/security/LDAPSecurityRealm/config.jelly b/src/main/resources/hudson/security/LDAPSecurityRealm/config.jelly index e69dd2e..e1886be 100644 --- a/src/main/resources/hudson/security/LDAPSecurityRealm/config.jelly +++ b/src/main/resources/hudson/security/LDAPSecurityRealm/config.jelly @@ -24,7 +24,7 @@ THE SOFTWARE. - + diff --git a/src/main/webapp/help-server.html b/src/main/webapp/help-server.html new file mode 100644 index 0000000..2939619 --- /dev/null +++ b/src/main/webapp/help-server.html @@ -0,0 +1,13 @@ +
+ Specify the name of the LDAP server host name(s) (like ldap.sun.com). + If your LDAP server uses a port other than 389 (which is the standard for LDAP), + you can also append a port number here, like ldap.acme.org:1389. + To connect to LDAP over SSL (AKA LDAPS), specify it with the ldaps:// protocol, + like ldaps://ldap.acme.org or ldaps://ldap.acme.org:1636 (if + the port is other than the default 636). +
+ Where there are multiple redundant servers separate them by spaces, if the first + named server is not available then requests will be attempted by each of the + named servers in order. NOTE: This is to support LDAP server fail-over, once an any + answer has been received from a server, that answer is taken as definitive +
\ No newline at end of file