> For the complete documentation index, see [llms.txt](https://docs.elimity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elimity.com/reference-manual/v3.44.5/built-in-connectors/ldif.md).

# LDIF

The LDIF connector for Elimity Insights imports users, groups and computers from an LDIF file so you can keep in control of your environment. Follow the instructions below to set up the connector for your environment.

## 1. Generate an LDIF export from your Active Directory tenant

This step is typically highly customer-specific. `ldifde` is a commonly used tool to generate LDIF exports, you can use the following example command as a starting point:

```powershell
PS C:\> Ldifde -f export.ldf -s dc.example.com
```

Store the resulting export file for later use.

## 2. Creating a source in Elimity Insights

In Elimity Insights you can now create a new LDIF source providing the following configuration options:

<table data-full-width="true"><thead><tr><th>Configuration option</th><th>Description</th></tr></thead><tbody><tr><td>file</td><td>Export file you generated in step 1.</td></tr></tbody></table>


---

# 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.elimity.com/reference-manual/v3.44.5/built-in-connectors/ldif.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.