{% with realm=ldap.realm %}

{% blocktranslate %}LDAP information, realm: {{ realm }}{% endblocktranslate %}¶

{% endwith %}

{% if ldap.error %}

{% trans "Error" %}

{% blocktrans %}Error while attempting to connect to LDAP server, base ldapsearch command is still displayed but won’t work as such.{% endblocktrans %}

{% if ldap.errmsg %}

{% blocktrans with errmsg=ldap.errmsg %}Server error: {{ errmsg }}{% endblocktrans %}

{% endif %}

{% blocktrans %}Base ldapsearch command{% endblocktrans %}

{% if ldap.require_cert != 'demand' %}LDAPTLS_REQCERT={{ldap.require_cert}} {% endif %}ldapsearch -v {% if ldap.error %}-d1 {% endif %}-H {{ ldap.ldap_uri }} \
    -D "{{ ldap.binddn }}" \
    -w "{{ ldap.bindpw }}" \
    -b "{{ ldap.basedn }}"{% if ldap.user_filter or ldap.sync_ldap_users_filter %} \
    "{% firstof ldap.sync_ldap_users_filter ldap.user_filter %}"{% endif %}

{% if ldap_https_proxy %}

{% blocktranslate trimmed %} Please note that the LDAP connection is configured to go through HTTPS proxy {{ ldap_https_proxy }}. Using a plain ldapsearch command could fail unless wrapped in a proxying utilitary (see for instance proxychains4 for Debian). {% endblocktranslate %}

{% endif %}

{% trans "Configuration" %}

{{ ldap.block }}