Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix Unexpected indentation error within the doc #1155

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from
Open

fix Unexpected indentation error within the doc #1155

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 9 additions & 12 deletions docs/manual/source/bind.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -225,18 +225,15 @@ or pass an appropriate value of the ``ReverseDnsSetting`` enum as the first elem


.. note::
`ldap3` currently support SASL authentication and data security layers for encryption.

If your server requires a string Security Strength Factor (SSF), you must enable data security layers using ``session_security=ENCRYPT``.

from ldap3 import KERBEROS, ENCRYPT, Connection
c = Connection(
server, authentication=SASL, sasl_mechanism=KERBEROS, session_security=ENCRYPT)

Plainmay receive
an ``LDAPStrongerAuthRequiredResult`` error when binding, e.g.:

SASL:[GSSAPI]: Sign or Seal are required.
`ldap3` currently support SASL authentication and data security layers for encryption. If your server requires a string Security Strength Factor (SSF), you must enable data security layers using ``session_security=ENCRYPT``.

.. code-block::

from ldap3 import KERBEROS, ENCRYPT, Connection
c = Connection(server, authentication=SASL,
sasl_mechanism=KERBEROS, session_security=ENCRYPT)

Plain
^^^^^
The PLAIN SASL mechanism sends data in clear text, so it must rely on other means of securing the connection between the client and the LDAP server.
As stated in RFC4616 the PLAIN mechanism should not be used without adequate data security protection as this mechanism affords no integrity or confidentiality
Expand Down