LogoLogo
LogoLogo
  • Welcome
  • Details
  • Editions
  • Use Cases
  • SCEPMAN Deployment
    • Getting Started
      • Standard Guide
      • Extended Guide
    • Permissions
      • Azure App Registration
      • Managed Identities
    • Deployment Options
      • Marketplace deployment
      • Enterprise deployment
      • Terraform deployment
    • Root CA
    • Intermediate CA
  • Certificate Management
    • Revocation
    • Microsoft Intune
      • Windows
        • Certificate Based Authentication for RDP
      • macOS
      • Android
      • iOS/iPadOS
      • Linux
    • Jamf Pro
      • General Configuration
      • Computers
      • Devices
      • Users
    • Other MDM Solutions
      • Google Workspace
        • ChromeOS
      • Kandji
      • Mosyle
      • SOTI MobiControl
    • Certificate Master
      • Manage Certificates
      • Certificate Signing Request (CSR)
      • TLS Server Certificate
      • Sub CA Certificate
      • Code Signing Certificate
      • Client Certificate
      • User Certificate
    • Domain Controller Certificates
    • Enrollment REST API
      • Self Service Enrollment
        • Intune Managed Linux Client
        • Unmanaged Linux Client
      • API Enrollment
        • Linux Server
        • Windows Server
      • SCEPmanClient
  • Azure Configuration
    • Application Insights
    • App Service Sizing
      • Autoscaling
    • Custom Domain
    • Geo-Redundancy
    • Health Check
      • Using 3rd Party Monitoring
    • Log Management
    • Moving Resources
    • Private Endpoints
    • Split-Tenancy
  • Update Strategy
  • SCEPman Configuration
    • SCEPman Settings
      • Basics
      • Certificates
      • Certificate Master
      • CRL
      • Dependencies (Azure Services)
        • Azure KeyVault
        • Logging
        • Microsoft Entra ID (Azure AD)
        • National Cloud Platforms
      • Enrollment REST API
      • OCSP
      • SCEP Endpoints
        • DC Validation
        • Intune Validation
        • Jamf Validation
        • Static Validation
        • Static-AAD Validation
    • Certificate Master Settings
      • Basics
      • Microsoft Entra ID (Azure AD)
      • Logging
      • National Cloud Platforms
    • Application Artifacts
    • Certificate Master RBAC
    • Device Directories
    • Intune Strong Mapping
  • Other
    • Security & Privacy
    • Support
    • Licensing
      • Azure Marketplace
    • FAQs
      • General
      • Certificate Connector
      • Network Access Controllers
      • Renewing SCEPman Root CA
    • Troubleshooting
      • Common Problems
      • Certifried Security Vulnerability
      • Cisco ISE Host Header Limitation
      • Intune service discovery API permissions
      • Re-enrollment trigger
  • Uninstallation
  • Change Log
  • Links
  • SCEPman Website
Powered by GitBook
On this page
  • AppConfig:StaticAADValidation:Enabled
  • AppConfig:StaticAADValidation:DefaultEkus
  • AppConfig:StaticAADValidation:DefaultKeyUsage
  • AppConfig:StaticAADValidation:RequestPassword
  • AppConfig:StaticAADValidation:ValidityPeriodDays
  • AppConfig:StaticAADValidation:EnableCertificateStorage

Was this helpful?

  1. SCEPman Configuration
  2. SCEPman Settings
  3. SCEP Endpoints

Static-AAD Validation

Last updated 25 days ago

Was this helpful?

SCEPman Enterprise customers only

These settings should only be applied to the SCEPman App Service, not the Certificate Master. Please refer to .

AppConfig:StaticAADValidation:Enabled

Linux: AppConfig__StaticAADValidation__Enabled

Applicable to version 2.2 and above

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 .

  • False (default): SCEPman does not issue AAD-bound certificates for Other MDM systems.

AppConfig:StaticAADValidation:DefaultEkus

Linux: AppConfig__StaticAADValidation__DefaultEkus

Applicable to version 2.8 and above

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 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

Applicable to version 2.8 and above

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

AppConfig:StaticAADValidation:RequestPassword

Linux: AppConfig__StaticAADValidation__RequestPassword

Applicable to version 2.2 and above

Value: String

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

Applicable to version 2.2 and above

Value: Positive Integer

AppConfig:StaticAADValidation:EnableCertificateStorage

Linux: AppConfig__StaticAADValidation__EnableCertificateStorage

Applicable to version 2.3 and above

SCEPman Enterprise Edition only

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.

Description: If a certificate request does not contain a Key Usage, SCEPman adds the Key Usage defined in this setting to the certificate. If 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.

Description: A challenge password that a Other MDM system must include in every SCEP request to acquire a certificate. Only used if is set to true.

Description: This setting further reduces the global for the Static-AAD endpoint.

AppConfig:StaticAADValidation:Enabled
SCEPman Settings
AppConfig:StaticAADValidation:RequestPassword
AppConfig:UseRequestedKeyUsages
AppConfig:UseRequestedKeyUsages
ValidityPeriodDays