Hi,
I support a large organisation's PKI and it's time for Issuing CA renewal against an offline Root CA. I manage the PKI but do not have Enterprise Admins nor have we delegated control of the Public Key Services container within the forest Configuration
partition.
I performed the usual renewal steps, selecting re-use keys (as we're confident of the current and future integrity, and wanted to ensure full compatibility), and generated a CSR (with suffix xxxx(1).req) which I duly presented to our offline CA, and received
a signed certificate. Let me point out at this stage that the offline Root CA is stored in a high security vault and is not that simple to just "get it out of the cupboard." I really don't want to go around this loop again, if
I can avoid it.
When attempting to install the certificate on the Issuing CA, I get:
"The new Certification Authority certificate cannot be installed because the CA Version extension is incorrect.The most recently generated request file should be used to obtain the new certificate:
C:\****-CA(1).req The data is invalid. 0x8007000d (WIN32: 13 ERROR_INVALID_DATA)"
I checked out the version identifier in the CSR and the certificate and it is indeed the same as the original:
CA Version
V0.0
I just assumed it would be the same as it's the same private key.
I guessed (and then read in another post) that this may be related to permissions so, today, we tried with Enterprise Admins permissions and still no go.
My question is this:
Can we manually deploy the CA certificate to the Configuration partition, the local CA store and then update the registry?
- certificateAuthority object.. Located in CN=AIA,CN=Public Key Services,CN=Services,CN=Configuration,DC=<var class="sbody-var">ForestRootDomain</var>
- certificationAuthority object.. Located in CN=Certification Authorities,CN=Public Key Services,CN=Services,CN=Configuration,DC=<var class="sbody-var">ForestRootDomain</var>
- If necessary, pKIEnrollmentService object.. Located in CN=Enrollment Services,CN=Public Key Services,CN=Services,CN=Configuration,DC=<var class="sbody-var">ForestRootDomain</var>
- If necessary, CN=NtAuthCertificates,CN=Public Key Services,CN=Services,CN=Configuration,DC=<var class="sbody-var">ForestRootDomain</var><var class="sbody-var"></var>
- Add the new CA cert into the Truisted Intermediaries store on the CA itself
- Thumbprint value into HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CertSvc\Configuration\"Name of your Certificate Authority"\CACertHash
Am I missing something?
I will raise a PSS call tomorrow under our Enterprise Agreement but I just wondered if anyone had solved this the hard way?
TIA
Dave