> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/piv-card-support/supporting-custom-ocsp-urls-for-piv-certificate-validation.md).

# Supporting custom OCSP URLs for PIV certificate validation

### Introduction

This procedure describes how to support custom OCSP URLs for PIV certificate validation.

This may be useful in the following scenarios:

* Specify OCSP download locations for certificates issued without an OCSP URL in the authority information access.

  If an organisation has previously deployed many certificates that did not include an OCSP URL, they can designate an OCSP download location instead of re-configuring the CA and reissuing all affected certificates.
* Override existing OCSP URLs in the authority information access with new locations.

  If an organisation has deployed internal OCSP URLs in their certificates and now wishes to use the certificates on the external network, the authority information access OCSP URLs must be updated with externally available URLs. Like specifying OCSP download locations for certificates without an OCSP URL, you can designate an externally available URL by using Group Policy or the Certificate Management Console.
* Use internal OCSP responder when firewall policies prevent network retrieval for revocation checking.

  Some networks do not enable connectivity to external networks. If a certificate was issued by an external provider, the lack of connectivity to external networks will prevent successful revocation checking. The clients can be redirected to an internally accessible OCSP URL for certificates issued by the external provider. Again, Group Policy or the Certificate Management Console can be used to designate the internally accessible URL for OCSP revocation checking.

### Procedure

The procedure below describes designating custom OCSP URLs on a Windows Server 2008 operating system:

1. Log on to a Domain Controller running Windows Server 2008 (or a computer running Windows Server 2008 with the Group Policy Management feature enabled) with a user account that can edit the certificate properties.
2. From the **Start** menu, click **Administrative Tools** > **Group Policy Management Editor**.
3. In the Console tree, expand **Forest:ForestName**, then expand **Domains**, and click **Domain**.
4. In the **Details** pane, right-click on **Default Domain Policy** and click **Edit**.

   **Note:** You can choose to implement the OCSP responder settings in any GPO.
5. In the **Group Policy Management Editor**, in the console tree, expand **Default Domain Policy**, expand **Computer Configuration**, expand **Policies**, expand **Windows Settings**, expand **Security Settings** and then expand **Public Key Policies**.

   <table><thead><tr><th width="202">If you are adding a...</th><th>then...</th></tr></thead><tbody><tr><td>Root CA certificate,</td><td>right-click <strong>Trusted Root Certification Authorities</strong>, and then click <strong>Import</strong>.</td></tr><tr><td>subordinate CA certificate,</td><td>right-click <strong>Intermediate Certification Authorities</strong>, and then click <strong>Import</strong>.</td></tr></tbody></table>
6. In the Certificate Import Wizard, click the **Next** button.
7. On the 'File to Import' page, in the **File name** field, type the full path of the new root or subordinate CA certificate, and then click the **Next** button.
8. On the 'Certificate Store' page, click the **Next** button.
9. On the 'Completing the Certificate Import Wizard' page, click the **Finish** button.
10. In the **Certificate Import Wizard** message box, click the **OK** button.
11. In the **Details** pane, right-click the newly imported certificate, and then click **Properties**.

    The CAName Properties dialog displays.
12. Click the **OCSP** tab, and define the appropriate options.

    You can either: 1) Disable CRLs, or 2) Add a custom OCSP responder URL.
13. Click the **OK** button after adding your custom OCSP URLs.
14. Close the **Group Policy Management Editor**, and then close the **Group Policy Management console**.

### Notes

* Designating custom OCSP URLs is per Certificate Authority (CA) based. This means you need to get the CA certificate and import it into the Windows Intermediate Certificate Authorities store. This won't be a problem in most cases because the CA certificate should be publicly available (either from the issuer or through the URL specified in the AIA extension of a PIV card certificate).
* If the custom OCSP responder goes offline, CryptoAPI will use the OCSP URL of the AIA extension for revocation checking. If there is no OCSP URL in the AIA extension or the OCSP responder is also offline, CryptoAPI will fallback to use the CRL URL of the CRL Distribution Points (CDP) extension.

### References

* Managing OCSP Settings with Group Policy. The link: [http://technet.microsoft.com/en-us/library/ee619786(v=ws.10).aspx](http://technet.microsoft.com/en-us/library/ee619786%28v=ws.10%29.aspx)
* Support for Independent OCSP Signer and Custom OCSP URLs. The link: [http://technet.microsoft.com/en-us/library/ee619784(v=ws.10).aspx](http://technet.microsoft.com/en-us/library/ee619784%28v=ws.10%29.aspx)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/piv-card-support/supporting-custom-ocsp-urls-for-piv-certificate-validation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
