> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/da/getting-started/security-checklist/ldap-over-ssl-ldaps.md).

# LDAP via SSL (LDAPS)

Aktivér LDAP via SSL (LDAPS) på port 636 for at kryptere katalogforespørgsler mellem Devolutions Server og Active Directory-domænecontrollere.

Brug af LDAP via SSL (LDAPS) sikrer, at legitimationsoplysninger og katalogforespørgsler, der udveksles mellem Devolutions Server og Active Directory, krypteres under overførsel.

#### Aktivér LDAPS

1. Konfigurer domænecontrollere til at acceptere LDAPS på port 636.
2. Undgå at bruge ukrypteret LDAP (port 389), undtagen i strengt kontrollerede undtagelsestilfælde.

#### Certifikatkrav

* Installér et gyldigt TLS-servercertifikat på hver domænecontroller, der bruges til godkendelse.

{% hint style="info" %}
Se [Certifikat til LDAP via SSL (LDAPS)](https://learn.microsoft.com/en-us/archive/technet-wiki/2980.ldap-over-ssl-ldaps-certificate) for at få flere oplysninger.
{% endhint %}

#### Test konfigurationen

1. Validér LDAPS-forbindelsen fra Devolutions Server-værten for at sikre korrekt certifikattillid og godkendelsesflow.
2. Dokumentér almindelige fejl (f.eks. certifikat, der ikke stemmer overens, eller udløbet certifikat) og trinnene til afhjælpning.

#### Planlægning af migrering

* Hvis Deres miljø i øjeblikket bruger LDAP i klartekst, skal De identificere ældre systemer og opgradere dem, før LDAPS håndhæves udelukkende.

#### Efterlevelse og bedste praksis

Mange lovgivningsmæssige rammer kræver krypteret katalogkommunikation. Håndhævelse af LDAPS mindsker eksponeringen for tyveri af legitimationsoplysninger, netværksafslytning og efterligningsangreb.


---

# 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.devolutions.net/server/da/getting-started/security-checklist/ldap-over-ssl-ldaps.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.