# Integrate an LDAP account database with Taiga

**URL:** https://community.taiga.io/t/integrate-an-ldap-account-database-with-taiga/212
**Category:** Third party
**Tags:** ldap
**Created:** [September 15, 2022, 9:38pm UTC](https://community.taiga.io/t/integrate-an-ldap-account-database-with-taiga/212 "2022-09-15T21:38:33Z")
**Posts on this page:** 1
**Showing post:** 68

<div class="post-metadata">

### Author: ![TuringTux](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/turingtux/32/309_2.png) [@TuringTux](https://community.taiga.io/u/TuringTux)
#### Post date: [June 10, 2025, 7:40pm UTC](https://community.taiga.io/t/integrate-an-ldap-account-database-with-taiga/212/68 "2025-06-10T19:40:14Z")

</div>

Not sure. If you can access the Taiga instance in the browser, and also see that you can send and receive to and from the API (which you proved by posting the network inspector screenshots), then the [script provided in my other answer](https://community.taiga.io/t/taiga-6-ldap-accounts-are-not-created/3497/2) should not give you any further information.

The next thing I would try is jumping into the backend container again and see if you can temporarily install `ldapsearch` there and execute a query against the LDAP server.

If it works, this means the problem must indeed be the LDAP plugin. If it does not work, likely something else is afoul with the communication.

# Test LDAP connection using base `ldap-utils`

1. Enter the container:

2. Install `ldap-utils`:

3. Start LDAP search:

4. Enter bind password:

5. Check exit status

The exit status should be `0` (success). If not, this means that not even Linux standard utilities can access the LDAP server from the backend container.

---

_[View the full topic](https://community.taiga.io/t/integrate-an-ldap-account-database-with-taiga/212)._