[SSSD] [PATCH] man: document the need to set ldap_access_order

Stephen Gallagher sgallagh at redhat.com
Mon Jun 10 12:20:25 UTC 2013


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon 10 Jun 2013 07:09:32 AM EDT, Ondrej Kos wrote:
> On 06/09/2013 01:41 PM, Jakub Hrozek wrote:
>> https://fedorahosted.org/sssd/ticket/1789
>> 
>> ldap_access_order must be set in order to non-default access
>> control options to work. This patch amends the sssd-ldap man page
>> to document this fact with all non-default ldap_access_order
>> options.

> 
> Ack from me, but some native speaker might check it as well,
> Stephen?
> 
> 
> 


The language looks fine. Ack


I can't help but wonder if we should change the defaults of
ldap_access_order to be

If ldap_access_filter has been set:
ldap_access_order = expire, filter

Otherwise:
ldap_access_order = expire


With this change, we could probably switch over to having the default
value for the access_provider be the id_provider, since the LDAP case
was the primary one that was at issue (since the default configuration
would not work).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlG1xIkACgkQeiVVYja6o6N9jgCgr5pWmTuNd8SZY2rOsm/BjDkj
3T4AoJTK8PDJKYaK+dDD0R4y9T7roJ4j
=3I2r
-----END PGP SIGNATURE-----



More information about the sssd-devel mailing list