Installing a Certificate Enrollment Policy Web Service (CEP)
The following describes how to install the Certificate Enrollment Policy Web Service (CEP).
Continue reading "Installing a Certificate Enrollment Policy Web Service (CEP)"
The following describes how to install the Certificate Enrollment Policy Web Service (CEP).
Continue reading "Installing a Certificate Enrollment Policy Web Service (CEP)"
The following describes how to set up a Certificate Enrollment Policy Web Service (CEP) so that the service runs under a domain account.
For security reasons, it may make sense to operate the CEP with a group managed service account (gMSA) instead of a normal domain account. This option offers the charming advantage that the password of the account is changed automatically, and thus this step does not have to be done manually, which is unfortunately forgotten far too often.
After a certificate enrollment policy is configured and used by a subscriber, the results are cached locally (Enrollment Policy Cache).
If changes are now made to the infrastructure, for example by publishing or removing a new certificate template on a certification authority accessible via Certificate Enrollment Web Service (CES), these changes are not immediately visible to subscribers due to the cache.
For this reason, it may be helpful to view or clear the cache.
When working with Certificate Enrollment Web Services and manually entering certificate enrollment policies on client computers, one encounters the phenomenon that there is no way to edit or delete them in the Certificates management console.
Continue reading "Deleting a Manually Configured Certificate Enrollment Policy (Enrollment Policy)"
Assume the following scenario:
The URI entered above has ID: "{{GUID}}". This ID conflicts with an existing ID.With Windows Server 2008 R2 and Windows 7, a new function for requesting certificates was introduced: The Certificate Enrollment Web Services, which are mapped by two server roles:
The following is a description of the background to these roles, how they work, and the possible deployment scenarios.
Assume the following scenario:
Error: The input data was not in the expected format or did not have the expected value. 0x803d0000 (-2143485952 WS_E_INVALID_FORMAT)Assume the following scenario:
Error: The remote endpoint is unable to process the request due to being overloaded. 0x803d0012 (-2143485934 WS_E_ENDPOINT_TOO_BUSY)Assume the following scenario:
Error: A message containing a fault was received from the remote endpoint. 0x803d0013 (-2143485933 WS_E_ENDPOINT_FAULT_RECEIVED)Assume the following scenario:
Error: The operation timed out 0x80072ee2 (WinHttp: 12002 ERROR_WINHTTP_TIMEOUT)