Posts on this page:
Hello world! Recently, a fellow guy asked a question why freshly registered OID is not visible in his app, while other applications see that OID. Today I will explain some nuiances on how AD-registered OIDs are propagated to clients and how OID caching works.
Every Windows installation ships OID (Object Identifier) mapping table, which divides various OIDs into a fixed set of OID groups:
| Group ID | Group Name | Description |
|---|---|---|
| 1 | HashAlgorithm | Contains hash algorithms, such as md2, md4, md5, SHA1, SHA256, SHA384, SHA512 and so on. |
| 2 | EncryptionAlgorithm | Contains symmetric encryption algorithms such as DES, 3DES, AES128, AES256 and so on. |
| 3 | PublicKeyAlgorithm | Contains public key algorithms, such as RSA, DSA, ECC, ECC curves, ML-DSA, ML-KEM and so on. |
| 4 | SignatureAlgorithm | Contains composite signature algorithms, such as sha1RSA, sha384ECDSA, ML-DSA-44, and so on. |
| 5 | Attribute | Contains X.520 RDN attributes, such as CN, E, C, Street, DC and so on. |
| 6 | ExtensionOrAttribute | Contains X.509 extension OIDs and CMS/PKCS#9 attributes, such as "Message Digest". |
| 7 | EnhancedKeyUsage | Self-explanatory, EKUs, such as "Server Authentication", "Code Signing" and so on. |
| 8 | Policy | Contains certificate policy OIDs, see RFC 5280 §4.2.1.4. Example: "All Issuance Policies" |
| 9 | Template | Contains ADCS certificate template OIDs. |
| 10 | KeyDerivationFunction | Contains KDF OIDs, such as ECDH_STD_SHA1_KDF |
Any OID in the table consist of four parts:
Hello everyone, I was silent for some time and today I'm back with some news.
It's official: AD CS ain't dead! On May 12, Active Directory Certificate Services (AD CS) got first PQC algorithm support, three flavors of ML-DSA:
In fact, PQC already was in BCrypt/NCrypt for some time, just not fully exposed through CNG, so you didn't see it in cryptographic provider properties.
PQC support in AD CS is added only to Windows Server 2025, starting with 2026.05B update (KB 5087539). As far as I know, there are no plans to update CertOCM (Certificate Organization Component Manager, or simply AD CS installer) for previous Windows Server, such as 2019 and 2022.
In this post, I'm not going to talk about PQC specifics in this post (I hope next time), I'll just focus on what new we will find in AD CS, certificate templates, certificate enrollment.
Hello world! Here is the fifth and the last part of an "AD CS Partitioned CRLs - A Comprehensive Guide" blog post series.
All posts in this series:
In this post, I will cover new programming APIs changes in existing API and Windows Event Log events associated with partitioned CRLs.
All programming APIs refer to ICertRequest2 and ICertAdmin2 COM interfaces, which are main interfaces to interact with AD CS servers.
ICertRequest2/ICertAdmin::GetCAProperty received several new PropID parameters that allow to access per-partition CRLs and their publishing statuses.
All new APIs work only when partitioned CRLs are globally enabled. If partitioned CRLs are not enabled, all mentioned below APIs will fail with HRESULT=0x80070057.
Hello S-1-1-0, here is the fourth part of an "AD CS Partitioned CRLs - A Comprehensive Guide" blog post series.
All posts in this series:
In previous post, I provided information about partitioned CRL design, description and configuration commands. This blog post will summarize this knowledge by providing quick guides to configure all partitioning strategies (A1, A2, B1 and B2) which you can use as a recipe template. Refer to Part 2 in this series for additional information aboud different CLR partitioning strategies.
This section will include configuration required by all subsequent sections.
Command examples include
CRLPublicationURLsconfig setting, which is provided as an example to point how<CRLPartitionIndex>variable is defined and new flags in front of HTTP URL. Adapt URLs to match your environment.
Hello world! Here is the third part of an "AD CS Partitioned CRLs - A Comprehensive Guide" blog post series.
All posts in this series:
In this part, I will explain Partitioned CRL configuration elements and their behavior.
In general, partitioned CRL consist of several configuration elements that MUST be configured in single batch. CA service will fail if any of mandatory configurations is not complete. Here is the list of all configuration options with indication which are mandatory:
The following sections will go through each configuration element.