> 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/dbcsr-validation.md).

# Enrollment REST API

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

Applicable to version 2.3.689 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 %}

## AppConfig:DbCSRValidation:Enabled

*Linux: AppConfig\_\_DbCSRValidation\_\_Enabled*

**Value:** *true* or *false* (default)

**Description:** This is a REST API endpoint that custom scripts and processes can use. See [our article on how to use the REST API](/certificate-management/api-certificates.md) for details.

## AppConfig:DbCSRValidation:ValidityPeriodDays

*Linux: AppConfig\_\_DbCSRValidation\_\_ValidityPeriodDays*

**Value:** Positive Integer

**Description:** This setting further reduces the global ValidityPeriodDays for the REST API endpoint. For example, you may define a value like 365 days here and set the global [AppConfig:ValidityPeriodDays](#appconfig-dbcsrvalidation-validityperioddays) to 730. Then, certificates issued through the API will have one year validity, while certificates issued through other endpoints may be valid up to two years.

Additionally, you can include an extension in your PKCS#10 requests to enroll certificates with a specific individual validity that is lower than the one configured here.

## AppConfig:DbCSRValidation:AllowRenewals

*Linux: AppConfig\_\_DbCSRValidation\_\_AllowRenewals*

**Value:** *true* or *false* (default)

**Description:** This allows using the EST "simplereenroll" endpoint, enabling [certificate renewal using mTLS](https://docs.scepman.com/certificate-deployment/api-certificates/api-enrollment#id-2.-app-service-settings). It works only for certificate types added to [AppConfig:DbCSRValidation:ReenrollmentAllowedCertificateTypes.](#appconfig-dbcsrvalidation-reenrollmentallowedcertificatetypes)

## AppConfig:DbCSRValidation:ReenrollmentAllowedCertificateTypes

*Linux: AppConfig\_\_DbCSRValidation\_\_ReenrollmentAllowedCertificateTypes*

**Value:** Comma-separated list of certificate types from this list:

* DomainController
* Static
* IntuneUser
* IntuneDevice
* JamfUser
* JamfUserWithDevice
* JamfUserWithComputer
* JamfDevice
* JamfComputer

**Description:** You can use the simplereenroll endpoint for certificates of the types specified in this setting. If you do not specifiy any value, it defaults to no types, i.e. you cannot use the simplereenroll endpoint.

For example, if you wanted to renew certificates issued manually through Certificate Master, you would specify `Static`. If you also want to renew Domain Controller certificates, you would specify `DomainController,Static`.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.scepman.com/scepman-configuration/application-settings/dbcsr-validation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
