> For the complete documentation index, see [llms.txt](https://docs.scepman.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scepman.com/fr/gestion-des-certificats/active-directory.md).

# Active Directory

{% hint style="warning" %}
SCEPman Enterprise Edition uniquement

Applicable à la version 3.0 et aux versions ultérieures
{% endhint %}

SCEPman peut être configuré pour traiter les requêtes SOAP provenant d’un client Windows afin de permettre une option de déploiement facile pour les clients joints à Active Directory qui ne peuvent être configurés qu’à l’aide de stratégies de groupe.

En créant un Service Principal dans votre environnement Active Directory sur site, nous pouvons permettre à SCEPman d’accepter les requêtes SOAP d’un client Windows joint au domaine demandant un certificat. Avec Kerberos utilisé comme protocole d’authentification, l’identité du demandeur peut être garantie et SCEPman répondra avec un certificat valide.

Toutes les versions prises en charge de Windows prennent en charge nativement cette méthode d’inscription et aucun logiciel supplémentaire n’est requis sur ces ordinateurs.

{% content-ref url="/pages/75eb0672e4c71739f6339b0a5bc75b86c4cb7a50" %}
[Configuration générale](/fr/gestion-des-certificats/active-directory/general-configuration.md)
{% endcontent-ref %}

{% content-ref url="/pages/ee6758bf1297b869379aed2078cc7185af6e0c0d" %}
[Stratégie de groupe](/fr/gestion-des-certificats/active-directory/group-policy.md)
{% endcontent-ref %}


---

# 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.scepman.com/fr/gestion-des-certificats/active-directory.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.