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

# Overview

AdminX Broker connects 1Kosmos to an existing Active Directory or LDAP directory so administrators can manage directory-backed accounts from AdminX.

***

### What is AdminX Broker?

AdminX Broker is a Linux-based connector that links 1Kosmos to your existing **Active Directory** or **LDAP** directory.

After you configure the connection, administrators manage directory-backed accounts from **AdminX** instead of handling them manually in 1Kosmos.

### Deployment notes

Use these deployment practices unless your environment requires otherwise:

* Do not install the broker as the Linux `root` account.
* Do not run multiple brokers on the same host.
* Keep the host dedicated and stable.

### Network and permissions

The broker needs the following access:

* Write permission to the installation directory
* Outbound connectivity to your tenant URL on TCP ports `80` and `443`
* A proxy URL if outbound traffic must pass through a proxy
* A **non-authenticated** proxy if a proxy is used


---

# 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.1kosmos.com/authentication/authentication-broker/overview.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.