a2b174
## BINDDN DN
a2b174
##  The BINDDN parameter specifies the identity, in the form of a Dis‐
a2b174
##  tinguished Name (DN), to use when performing LDAP operations.  If
a2b174
##  not specified, LDAP operations are performed with an anonymous
a2b174
##  identity.  By default, most LDAP servers will allow anonymous
a2b174
##  access.
a2b174
##
a2b174
#binddn uid=sudo,cn=sysaccounts,cn=etc,dc=example,dc=com
a2b174
a2b174
## BINDPW secret
a2b174
##  The BINDPW parameter specifies the password to use when performing
a2b174
##  LDAP operations.  This is typically used in conjunction with the
a2b174
##  BINDDN parameter.
a2b174
##
a2b174
#bindpw secret
a2b174
a2b174
## SSL start_tls
a2b174
##  If the SSL parameter is set to start_tls, the LDAP server connec‐
a2b174
##  tion is initiated normally and TLS encryption is begun before the
a2b174
##  bind credentials are sent.  This has the advantage of not requiring
a2b174
##  a dedicated port for encrypted communications.  This parameter is
a2b174
##  only supported by LDAP servers that honor the start_tls extension,
a2b174
##  such as the OpenLDAP and Tivoli Directory servers.
a2b174
##
a2b174
#ssl start_tls
a2b174
a2b174
## TLS_CACERTFILE file name
a2b174
##  The path to a certificate authority bundle which contains the cer‐
a2b174
##  tificates for all the Certificate Authorities the client knows to
a2b174
##  be valid, e.g. /etc/ssl/ca-bundle.pem.  This option is only sup‐
a2b174
##  ported by the OpenLDAP libraries.  Netscape-derived LDAP libraries
a2b174
##  use the same certificate database for CA and client certificates
a2b174
##  (see TLS_CERT).
a2b174
##
a2b174
#tls_cacertfile /path/to/CA.crt
a2b174
a2b174
## TLS_CHECKPEER on/true/yes/off/false/no
a2b174
##  If enabled, TLS_CHECKPEER will cause the LDAP server's TLS certifi‐
a2b174
##  cated to be verified.  If the server's TLS certificate cannot be
a2b174
##  verified (usually because it is signed by an unknown certificate
a2b174
##  authority), sudo will be unable to connect to it.  If TLS_CHECKPEER
a2b174
##  is disabled, no check is made.  Note that disabling the check cre‐
a2b174
##  ates an opportunity for man-in-the-middle attacks since the
a2b174
##  server's identity will not be authenticated.  If possible, the CA's
a2b174
##  certificate should be installed locally so it can be verified.
a2b174
##  This option is not supported by the Tivoli Directory Server LDAP
a2b174
##  libraries.
a2b174
#tls_checkpeer yes
a2b174
a2b174
##
a2b174
## URI ldap[s]://[hostname[:port]] ...
a2b174
##  Specifies a whitespace-delimited list of one or more
a2b174
##  URIs describing the LDAP server(s) to connect to. 
a2b174
##
a2b174
#uri ldap://ldapserver
a2b174
a2b174
##
a2b174
## SUDOERS_BASE base
a2b174
##  The base DN to use when performing sudo LDAP queries.
a2b174
##  Multiple SUDOERS_BASE lines may be specified, in which
a2b174
##  case they are queried in the order specified.
a2b174
##
a2b174
#sudoers_base ou=SUDOers,dc=example,dc=com
a2b174
a2b174
##
a2b174
## BIND_TIMELIMIT seconds
a2b174
##  The BIND_TIMELIMIT parameter specifies the amount of
a2b174
##  time to wait while trying to connect to an LDAP server.
a2b174
##
a2b174
#bind_timelimit 30
a2b174
a2b174
##
a2b174
## TIMELIMIT seconds
a2b174
##  The TIMELIMIT parameter specifies the amount of time
a2b174
##  to wait for a response to an LDAP query.
a2b174
##
a2b174
#timelimit 30
a2b174
a2b174
##
a2b174
## SUDOERS_DEBUG debug_level
a2b174
##  This sets the debug level for sudo LDAP queries. Debugging
a2b174
##  information is printed to the standard error. A value of 1
a2b174
##  results in a moderate amount of debugging information.
a2b174
##  A value of 2 shows the results of the matches themselves.
a2b174
##
a2b174
#sudoers_debug 1