# Static-AAD Validation

{% hint style="warning" %}
SCEPman Enterprise customers only
{% endhint %}

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

## AppConfig:StaticAADValidation:Enabled

*Linux: AppConfig\_\_StaticAADValidation\_\_Enabled*

{% hint style="info" %}
Applicable to version 2.2 and above
{% endhint %}

**Value:** *true* or *false*

**Description:** This setting helps you to request certificates from Other MDM systems, similarly to the static endpoint, but the certificates' lifetimes are bound to AAD objects (users or devices). The certificate subject has to include an AAD device ID or the Subject Alternative Name must include a user's UPN, just like for Intune certificates.

* **True**: SCEPman listens at the additional SCEP server endpoint with the path `/static/aad`. Use in conjunction with [AppConfig:StaticAADValidation:RequestPassword](#appconfig-staticaadvalidation-requestpassword). 
* **False** (default): SCEPman does not issue AAD-bound certificates for Other MDM systems.

## AppConfig:StaticAADValidation:DefaultEkus

*Linux: AppConfig\_\_StaticAADValidation\_\_DefaultEkus*

{% hint style="info" %}
Applicable to version 2.8 and above
{% endhint %}

**Value:** Oids of the extended key usages (EKUs) that are added to the certificate if the Static AAD endpoint is used. The Oids are separated by a comma, semicolon, or space. The default is Client Authentication (1.3.6.1.5.5.7.3.2)

**Description:** If a certificate request does not contain any EKUs, SCEPman adds the EKUs defined in this setting to the certificate. If [AppConfig:UseRequestedKeyUsages](https://docs.scepman.com/scepman-configuration/certificates#appconfig-userequestedkeyusages) is set to *false*, the EKUs defined in this setting will be added to the certificate even if the certificate request contains EKUs.

## AppConfig:StaticAADValidation:DefaultKeyUsage

*Linux: AppConfig\_\_StaticAADValidation\_\_DefaultKeyUsage*

{% hint style="info" %}
Applicable to version 2.8 and above
{% endhint %}

**Value:** EncipherOnly|CrlSign|KeyCertSign|KeyAgreement|DataEncipherment|*KeyEncipherment*|NonRepudiation|*DigitalSignature*|DecipherOnly (defaults are in *italic*)

**Description:** If a certificate request does not contain a Key Usage, SCEPman adds the Key Usage defined in this setting to the certificate. If [AppConfig:UseRequestedKeyUsages](https://docs.scepman.com/scepman-configuration/certificates#appconfig-userequestedkeyusages) is set to *false*, the Key Usage defined in this setting will be added to the certificate even if the certificate request contains a Key Usage.

## AppConfig:StaticAADValidation:RequestPassword

*Linux: AppConfig\_\_StaticAADValidation\_\_RequestPassword*

{% hint style="info" %}
Applicable to version 2.2 and above
{% endhint %}

**Value:** *String*

**Description:** A challenge password that a Other MDM system must include in every SCEP request to acquire a certificate. Only used if [AppConfig:StaticAADValidation:Enabled](#appconfig-staticaadvalidation-enabled) is set to *true*.

We recommend defining this setting as Secret in Azure Key Vault. The Secret must have the name *AppConfig--StaticAADValidation--RequestPassword*.

## AppConfig:StaticAADValidation:ValidityPeriodDays

*Linux: AppConfig\_\_StaticAADValidation\_\_ValidityPeriodDays*

{% hint style="info" %}
Applicable to version 2.2 and above
{% endhint %}

**Value:** Positive *Integer*

**Description:** This setting further reduces the global [ValidityPeriodDays](https://docs.scepman.com/scepman-configuration/certificates#appconfig-validityperioddays) for the Static-AAD endpoint.

## AppConfig:StaticAADValidation:EnableCertificateStorage

*Linux: AppConfig\_\_StaticAADValidation\_\_EnableCertificateStorage*

{% hint style="info" %}
Applicable to version 2.3 and above

SCEPman Enterprise Edition only
{% endhint %}

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

**Description:** When requesting certificates via the Static-AAD endpoint, SCEPman stores those requested certificates in the Storage Account in Azure if this is set to *true*. This will make the issued certificates appear in SCEPman Certificate Master, where you can view and revoke them manually. Additionally, certificates are revoked automatically if the corresponding AAD object is disabled or deleted. If set to *false* or not set, SCEPman will not store issued certificates and the certificates are visible only in the logs or if the SCEP client stores them somewhere.