> For the complete documentation index, see [llms.txt](https://docs.frends.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frends.com/tasks/tasks/ldap.md).

# LDAP

LDAP is a protocol used to access and manage directory information, such as user identities.

Frends offers seamless integration with LDAP(S) (Lightweight Directory Access Protocol), enabling you to effortlessly connect and manage directory services and user information using LDAP(S).

Frends has tasks for performing all core LDAP(S) operations.

By leveraging Frends' task-based approach, you can configure and customize LDAP(S) integrations according to your specific requirements. Frends offers a wide range of tasks that facilitate integrations to a variety of systems and protocols.

## Use cases

Below you will find typical use cases for LDAP(S) integrations and how they are implemented in Frends.

### Update user information periodically

By using a schedule trigger and the [`LDAP UpdateUser`](/tasks/tasks/ldap/updateuser.md) task, we can create an integration that periodically updates user attributes in the LDAP(S) directory based on data changes in a connected system.

<figure><img src="https://2096450325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FevBo49UTUjEN84O2WPl6%2Fuploads%2Fgit-blob-205b108116558d8badde3503fcfd1abd8673f968%2Fldap-update-user.svg?alt=media&amp;token=cb98beed-9f6f-4f65-a846-8b1e62c23f60" alt=""><figcaption><p>Update user</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.frends.com/tasks/tasks/ldap.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
