[Bps-public-commit] rt-authen-externalauth branch, master, updated. 0.20-1-gf954bed

[Kevin Falcone]

The branch, master has been updated
       via  f954beddbbb5586c424fc12adae400c9bf554042 (commit)
      from  0f557fd01fc1a3adc147646fa82b9811929e8ce9 (commit)

Summary of changes:
 lib/RT/Authen/ExternalAuth/LDAP.pm | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

- Log -----------------------------------------------------------------
commit f954beddbbb5586c424fc12adae400c9bf554042
Author: Kevin Falcone <falcone at bestpractical.com>
Date:   Wed May 28 21:17:29 2014 -0400

    Don't just blindly say "use anonymous binds"
    
    Instead point out that it's an option, but also point out the problems.

diff --git a/lib/RT/Authen/ExternalAuth/LDAP.pm b/lib/RT/Authen/ExternalAuth/LDAP.pm
index 2118c7d..af5bc82 100644
--- a/lib/RT/Authen/ExternalAuth/LDAP.pm
+++ b/lib/RT/Authen/ExternalAuth/LDAP.pm
@@ -82,8 +82,11 @@ The server hosting the LDAP or AD service.
 The username and password RT should use to connect to the LDAP
 server.
 
-If you can bind to your LDAP server anonymously you shouldn't
-set these options.
+If you can bind to your LDAP server anonymously you may be able to omit these
+options.  Many servers do not allow anonymous binds, or restrict what information
+they can see or how much information they can retrieve.  If your server does not
+allow anonymous binds then you must have a service account created for this
+extension to function.
 
 =item base
 

-----------------------------------------------------------------------