> 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/scepman-configuration/application-settings/active-directory.md).

# Active Directory

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

Applicable to version 3.0 and above
{% endhint %}

{% hint style="info" %}
These settings should only be applied to the SCEPman App Service, not the Certificate Master. Please refer to [SCEPman Settings](/scepman-configuration/application-settings.md).
{% endhint %}

## General Settings

The following settings affect the behavior of the Active Directory endpoint in general.

{% content-ref url="/pages/fxYRQ8tdRF9SK784z4ds" %}
[General](/scepman-configuration/application-settings/active-directory/general.md)
{% endcontent-ref %}

## Certificate Templates

Aside from the general settings of the endpoint, the certificate templates can be configured independently. The format of those variable names follow the scheme `AppConfig:ActiveDirectory:[Template]:[Setting]` where `[Template]` is to be replaced with User, Computer or DC and `[Setting]` is to be replaced with the respective setting name. You can find the configuration options for the certificate templates in the following pages.

{% content-ref url="/pages/zaZtGd4iOGTIJ1kmZY40" %}
[User Template](/scepman-configuration/application-settings/active-directory/user-template.md)
{% endcontent-ref %}

{% content-ref url="/pages/nhvwYEAx3TR1DcQiCFn3" %}
[Computer Template](/scepman-configuration/application-settings/active-directory/computer-template.md)
{% endcontent-ref %}

{% content-ref url="/pages/KJ8oFbXhys2rU3EdUiHa" %}
[DC Template](/scepman-configuration/application-settings/active-directory/dc-template.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/scepman-configuration/application-settings/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.