diff options
| author | Sumit Bose <sbose@redhat.com> | 2010-11-19 10:38:32 +0100 |
|---|---|---|
| committer | Stephen Gallagher <sgallagh@redhat.com> | 2010-11-19 13:52:24 -0500 |
| commit | b7b8995f3cd6af74f9a87548dc0ee9b555b2043c (patch) | |
| tree | e9f8279adc8fc057a338521d517c838d45a6e71c | |
| parent | 488f1784198a0a8775d7f5bb9e960d80a833ba73 (diff) | |
| download | sssd-b7b8995f3cd6af74f9a87548dc0ee9b555b2043c.tar.gz sssd-b7b8995f3cd6af74f9a87548dc0ee9b555b2043c.tar.bz2 sssd-b7b8995f3cd6af74f9a87548dc0ee9b555b2043c.zip | |
Fix man page
Currently sssd does not support authentication via GSSAPI. I think it
is not necessary to support it, because if GSSAPI is possible Kerberos
should be use for authentication.
| -rw-r--r-- | src/man/sssd-ldap.5.xml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/man/sssd-ldap.5.xml b/src/man/sssd-ldap.5.xml index 416cd778..a30b49d1 100644 --- a/src/man/sssd-ldap.5.xml +++ b/src/man/sssd-ldap.5.xml @@ -36,8 +36,8 @@ </para> <para> LDAP back end supports id, auth, access and chpass providers. If you want - to authenticate against an LDAP server either TLS/SSL, LDAPS, or - LDAP+GSSAPI is required. <command>sssd</command> <emphasis>does + to authenticate against an LDAP server either TLS/SSL or LDAPS + is required. <command>sssd</command> <emphasis>does not</emphasis> support authentication over an unencrypted channel. If the LDAP server is used only as an identity provider, an encrypted channel is not needed. Please refer to <quote>ldap_access_filter</quote> |