mir/sudo
2
0
Fork 0
mirror of https://github.com/sudo-project/sudo.git synced 2025-08-22 09:57:41 +00:00
Code Issues Releases Wiki Activity

Make it clear that host and uri can take multiple parameters.

Browse Source 
URI is now supported for more than just openldap
nsswitch.conf does't accept "compat"
This commit is contained in:
Todd C. Miller 2008-01-05 21:35:25 +00:00
parent 055bda6261
commit 77d841e0e6
1 changed files with 8 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
README.LDAP
View File

@ -212,15 +212,19 @@ option.
Make sure you sudoers_base matches exactly with the location you specified
when you imported the sudoers. Below is an example /etc/ldap.conf
# Either specify a URI or host and port.
# If neither is specified sudo will default to localhost port 389.
# Either specify one or more URIs or one or more host:port pairs.
# If neither is specified sudo will default to localhost, port 389.
#
#host ldapserver
#host ldapserver1 ldapserver2:390
#
# Default port if host is specified without one, defaults to 389.
#port 389
#
# URI will override host & port settings but only works with LDAP
# SDK's that support ldap_initialize() such as OpenLDAP.
# URI will override the host and port settings.
uri ldap://ldapserver
#uri ldaps://secureldapserver
#uri ldaps://secureldapserver ldap://ldapserver
#
# must be set or sudo will ignore LDAP
sudoers_base ou=SUDOers,dc=example,dc=com
@ -372,7 +376,6 @@ Starting with version 1.7, sudo consults nsswitch.conf for the search order.
The following sources are recognized.
files read sudoers from a file (usually /etc/sudoers)
ldap read sudoers from LDAP
compat behave as if no nsswitch.conf was present
I addition, the entry "[NOTFOUND=return]" will short-circuit the
search if the user was not found in the preceding source.