CRL Download via SCEP fails in CA multi tier Hierarchy (Two tier / Three tier) with Event ID : 45 (NDES cannot match the issuer and serial number in the device request with any CA certificate)


hi all,

operating system - windows server 2012 r2

we have set 3 tier ca hierarchy.

root ca->subca->issuing ca

ndes service installed @ issuing ca.

we have developed client application retrieve crl issuing ca via scep protocol.

we error "transaction not permitted or supported" reply in client issuing ca ndes. on viewing event viewer @ issuing ca, can see

"event id : 45, says "ndes cannot match issuer , serial number in device request certification authority (ca) certificate"

--------------------------------

we have reviewed implementation of client multiple times. filling issuer , serial number information "issuing ca certificate" device crl download request. testing purpose, have tried fill same "ca root certificate" "enrolled certificate device received signed issuing ca".

the same error happens 2 tier hierarchy well.

--------------------------------------------------------

however crl retrieval works fine single tier hierarchy via scep.

here using ca root certificate fill in issuer , serial information in device request.

any ideas solve problem helpful.

is there additional settings required make work in multi hierarchy set up? or should use other certificate fill in issuer , serial number information in device request.

any appreciated. in advance.


great day, sreekanth


hi,

>>we have reviewed implementation of client multiple times. filling issuer , serial number information "issuing ca certificate" device crl download request.

according following draft, messagedata type consists of issuerandserial along issuer name   , serial number certificate validated.

https://tools.ietf.org/html/draft-nourse-scep-23#section-3.2.5

it seems question more related coding, suggest contact microsoft customer support , services more in-depth investigation can done more satisfying explanation , solution issue.
in addition, if issue has been proved system flaw, consulting fee refund.
may find phone number region accordingly link below:
global customer service phone numbers
https://support.microsoft.com/en-us/gp/customer-service-phone-numbers/en-au?wa=wsignin1.0

best regads.


steven lee please remember mark replies answers if , unmark them if provide no help. if have feedback technet support, contact tnmff@microsoft.com.



Windows Server  >  Security



Comments

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

Failed to delete the test record dcdiag-test-record in zone test.com

Azure MFA with Azure AD and RDS