Skip to content

Commit ec2b623

Browse files
committed
[TASK][DOC] Describe workaround for untrusted LDAP server certificate
Related: #82658 Change-Id: Icf65c6eeb6829fc1a31aa52d40baab09289c03e1 Reviewed-on: https://review.typo3.org/54280 Reviewed-by: Xavier Perseguers <[email protected]> Tested-by: Xavier Perseguers <[email protected]>
1 parent 39dcbfb commit ec2b623

File tree

1 file changed

+10
-0
lines changed
  • Documentation/AdministratorManual

1 file changed

+10
-0
lines changed

Documentation/AdministratorManual/Ldap.rst

+10
Original file line numberDiff line numberDiff line change
@@ -75,6 +75,16 @@ SSL
7575
Whether you want to use :abbr:`SSL (Secure Socket Layer)`, that is start with an encrypted connection on default port
7676
636.
7777

78+
.. note::
79+
Some web servers may fail at connecting to the LDAP server since they report that the server certificate is
80+
untrusted (although issued by a valid CA such as Letsencrypt). In case this happens and you cannot change the web
81+
server configuration (e.g., shared hosting), you may add this line to :file:`typo3conf/AdditionalConfiguration.php`:
82+
83+
.. code-block:: php
84+
85+
// Always trust the LDAP server certificate
86+
putenv('LDAPTLS_REQCERT=never');
87+
7888
7989
.. _admin-manual-ldap-binddn:
8090

0 commit comments

Comments
 (0)