> 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/editing-the-piv-card-type.md).

# Editing the PIV Card Type

### Introduction

When a site is licensed for Personal Identity Verification (PIV), a PIV card type is available by default in the Card Type List Window. The PIV card type is a special card type for the exclusive use of PIV and PIV-I cards, and is not creatable, (i.e. only one PIV card type record will exist, and cannot be deleted, copied or created manually).

Operators require the "Configure Site" privilege in the appropriate division to be able to edit the PIV Card Type.

**Note:** The "View Site" privilege in the appropriate division will allow an operator to view (but not edit) the PIV Card Type.

***

### Procedure

To edit the PIV Card Type, perform the following procedures in Gallagher Configuration Client:

1. Click **Configure** from the menu bar, then **Card Types**.

   The **Card Type** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)), with the "PIV Card" appearing by default.
2. **Right click** on the "PIV Card" and select **Properties**.

   By default the **General** tab displays.
3. Edit the **Description** and the **Division** that the PIV card type exists in if required.

   **Note:** The **Name** is non-editable, and therefore disabled.
4. Click each tab in turn to edit the PIV Card Type:

<details>

<summary>Setup tab</summary>

1. Click the **Setup** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-dc43931054853707efcff40895197db7960b8b13%2Fpivcard_setuptab.png?alt=media)
2. Do you wish to enable the Inactive Card Expiry feature?

   **Note:** All cards of a particular type shall share a common inactivity timeout if enabled.

   <table><thead><tr><th width="60">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes</td><td><p>check the <strong>Disable Inactive Cards</strong> checkbox.</p><p>Go to Step 3.</p></td></tr><tr><td>no</td><td><p>leave the <strong>Disable Inactive Cards</strong> checkbox unchecked.</p><p>Go to Step 4.</p></td></tr></tbody></table>
3. Enter a figure to represent the number of days of inactivity that will disable a card.

   **Notes:**

   * When this feature is first enabled the default timeout = 30 days. The range is 1 - 999 days.
   * If you set a card type to disable after 1 day of inactivity, these cards will become disabled 24 hours to the second after the **Apply** button is clicked, (e.g. card type set on 27/11/2011 at 16:10:15; if not used these cards become disabled on 28/11/2011 at 16:10:15).
   * Cardholders will be expired regardless of activity if card activity events are not configured to log events throughout the site (see [Event Defaults](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/event-defaults.md) for further detail).
4. The **Enable card expiry notification** section of this screen allows you to configure warning notifications of pending card expiry to be sent when the specified period is reached, for all cards regardless of status.

   Do you want to enable card expiry notification?

   <table><thead><tr><th width="60">If...</th><th>then...</th></tr></thead><tbody><tr><td>no</td><td>uncheck the <strong>Enable card expiry notification</strong> checkbox, and leave the <strong>Advance notice period</strong> as 0 Days.</td></tr><tr><td>yes</td><td><ol><li>Ensure the <strong>Enable card expiry notification</strong> checkbox remains checked.</li><li>Set the Advance notice period to the value that is required to represent the number of days, weeks, months or years prior to card expiry to initiate the warning notification.</li></ol></td></tr></tbody></table>

</details>

<details>

<summary>PINs tab</summary>

1. Click the **PINs** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5f74d03e911a4c7128c4618ab9fefe23879af009%2Fpivcard_pinstab.png?alt=media)
2. If you want to use PINs, check the **Use PINs** checkbox and set the **Minimum PIN length**.

   (Default = 6 digits. Range = 4 - 8 digits)

   **Notes:**

   * If you do not choose to **Use PINs**, the **Assign PIN** button on the Cardholder Cards tile in Command Centre Client will be disabled.
   * The maximum PIN length is **8** digits. There is no mechanism to reduce the maximum size. Hence if a site sets minimum at 4, the user can enter PIN length anywhere from 4 to **8** digits.
   * The system prevents PINs with 3 consecutive or 3 repeating numbers from being either manually entered or automatically generated.

</details>

<details>

<summary>Certificate Validation tab</summary>

1. Click the **Certificate Validation** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-bad00d81cc4028bca99144e6fa36d78eb97d6004%2Fpivcard_certvalidationtab.png?alt=media)
2. The **Period of Validation** can either be specified in hours, it can occur immediately, or it can be turned off.

   <table><thead><tr><th width="198">If you want to...</th><th>then...</th></tr></thead><tbody><tr><td>change the period of validation,</td><td><ol><li>Click the <strong>every</strong> radio button.</li><li><p>Select the appropriate number from the <strong>hours</strong> drop-down for the period between validation occurrences.</p><p>(Default = 12 hours. Range = 1, 2, 3, 4, 6, 8, 12, 24 hours)</p></li><li>Go to Step 3.</li></ol></td></tr><tr><td>validate immediately,</td><td><ol><li><p>Click the <strong>Validate Now</strong> button.</p><p><strong>Note:</strong> Validations cannot be run concurrently. If one is already running the message <em>"A validation is already in progress"</em> will display.</p></li><li>Go to Step 3.</li></ol></td></tr><tr><td>turn validation off,</td><td><ol><li><p>Click the <strong>Never</strong> radio button.</p><p>The <strong>Initial Certificate Validation Time</strong> is disabled.</p></li><li><p>Go to Step 4.</p><p><strong>IMPORTANT:</strong> Clicking the <strong>Never</strong> radio button turns off all validation, not just for cards subsequently enrolled. It does not reinstate disabled cards from a previous validation where they have failed.</p></li></ol></td></tr><tr><td colspan="2"><p><strong>Notes:</strong></p><ul><li>If certificate validation is still occurring at the time of the next validation scheduled start time, the next validation will be skipped, and an event is raised indicating that a validation cycle has been skipped.</li><li>If the Command Centre service is restarted after the cards are enrolled but before any validation has occurred, (i.e. validation has NOT been turned off), automatic validation on enrolment will never occur.</li><li><p>When the validation process results in Command Centre recognising that a PIV card's PIV, CAK or Issuer Signature certificate is invalid, the following occurs:</p><ul><li>the card cannot be used to gain access,</li><li>an Alarm is raised, and</li><li>the card is marked with the status <strong>Revoked</strong>, <strong>Expired</strong> or <strong>Not Trusted</strong>.</li></ul><p><strong>Note:</strong> Cards with a status of <strong>Revoked</strong> or <strong>Expired</strong> must be re-enrolled. If a root certificate is added to the Windows Certificate Store and the Selected Trusted Root Certificates listbox relating to a card with a status of <strong>Not Trusted</strong>, the card will become <strong>Active</strong> and can be used after the next successful validation.</p></li></ul></td></tr></tbody></table>
3. When Command Centre is licensed for PIV the first credential/path validation check will occur at the next occurrence of the **Initial Certificate Validation Time**.

   The default for this control is 07:00 (7am).

   **Notes:**

   * When the **Initial Certificate Validation Time** is changed, the validation will start at the next occurrence of that daily time, and subsequent validation will begin based on the period.
   * For the validation checks via internet you need to run the Command Centre service as a user who has access to the internet. This may also require some configuration by your IT Department.
4. The **Validation of Issuer Signature Certificates** section on this tab provides a list of certificate issuers with an option to exclude/ignore validation of expired Issuer Signature certificates when the card has not expired. By default all checkboxes are enabled and deselected, so that when a card is not expired, all Issuer's Issuer Signature certificates are validated regardless of the expiry status of the certificate.

   **Note:** Use this feature in the event that PIV Card Issuers have issued cards that expire after the expiry of certificates higher in the certificate chain, if you do not wish such cards to be considered revoked.
5. Check the **Ignore Certificate Expiry** checkbox for Card Issuer(s), as required.

   **Note:** When the **Ignore Certificate Expiry** checkbox is checked for a particular Card Issuer, if a card has not expired but that Issuer's Issuer Signature certificate has expired, the validation will not run for that certificate.

</details>

<details>

<summary>Trusted Root Certificates tab</summary>

1. Click the **Trusted Root Certificates** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-4b9e639add4e85df03edd7ae1a1ea2896ed8185e%2Fpivcard_trustedrootcertstab.png?alt=media)

   This tab allows you to explicitly add Trusted Root Certificates that exist in the server's certificate store.

   The 'Available Trusted Root Certificates' grid is populated with all Trusted Root Certification Authority certificates available to the server in the Windows certificate store.
2. Drag any of the certificates you require from the 'Available Trusted Root Certificates' grid across to the 'Selected Trusted Root Certificates' grid.

   **Notes:**

   * If a required certificate does not appear in the 'Available Trusted Root Certificates' grid, see [Setup Certificate Manager](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/piv-card-support/editing-the-piv-card-type/setup-certificate-manager.md) for instructions on how to import it into the list.
   * When a certificate is added to the 'Selected Trusted Root Certificates' grid, the certificate is removed from the 'Available Trusted Root Certificates' grid. When a certificate is removed from the 'Selected Trusted Root Certificates' grid (via a right click and selecting **Remove from List** ), the certificate reappears in the 'Available Trusted Root Certificates' grid.
   * When a PIV card is presented at a reader it must have its Trusted Root Certificate explicitly selected before access can be granted. If not, a 'Certificate Not Trusted' event will be raised.

</details>

<details>

<summary>Validation Options tab</summary>

1. Click the **Validation Options** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6349c61386cefd28d02f66b17b496bd1e4a2c5ff%2Fpivcard_validationoptionstab.png?alt=media)

   This tab provides options to ignore validation faults that can make a card unusable due to certificate errors. The options are as follows:

   <table><thead><tr><th width="148" valign="top">Checkbox</th><th width="166" valign="top">Type of fault</th><th width="91" valign="top">Checked?</th><th width="180" valign="top">Outcome: Fault is ignored</th><th width="180" valign="top">Outcome: Card remain in normal (Active) status</th><th width="180" valign="top">Outcome: Card flagged as "card certificate error" status during validation</th><th width="180" valign="top">Outcome: Card flagged as "certificate status unknown"</th><th width="180" valign="top">Outcome: Card can still be used for access</th></tr></thead><tbody><tr><td rowspan="2" valign="top">Ignore missing CRL (Certificate Revocation List) file</td><td rowspan="2" valign="top">Missing CRL file fault</td><td valign="top"><i class="fa-square">:square:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td></tr><tr><td valign="top"><i class="fa-square-check">:square-check:</i> Yes</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td></tr><tr><td rowspan="2" valign="top">Ignore mismatched SKID in the certificate chain</td><td rowspan="2" valign="top">Mismatched SKID fault</td><td valign="top"><i class="fa-square">:square:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td></tr><tr><td valign="top"><i class="fa-square-check">:square-check:</i> Yes</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td></tr><tr><td rowspan="2" valign="top">Use strict AKID chaining</td><td rowspan="2" valign="top">Mismatched AKID fault</td><td valign="top"><i class="fa-square">:square:</i> No</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td></tr><tr><td valign="top"><i class="fa-square-check">:square-check:</i> Yes</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td></tr><tr><td rowspan="2" valign="top">Enforce critical keyUsage extension</td><td rowspan="2" valign="top">Non-critical keyUsage extension fault</td><td valign="top"><i class="fa-square">:square:</i> No</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td></tr><tr><td valign="top"><i class="fa-square-check">:square-check:</i> Yes</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td></tr><tr><td rowspan="2" valign="top">Ignore strict name chaining</td><td rowspan="2" valign="top">Mismatched issuer common name fault in the certificate</td><td valign="top"><i class="fa-square">:square:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td></tr><tr><td valign="top"><i class="fa-square-check">:square-check:</i> Yes</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td></tr><tr><td rowspan="2" valign="top">Ignore strict name chaining in CRL</td><td rowspan="2" valign="top">Mismatched issuer common name fault in the CRL</td><td valign="top"><i class="fa-square">:square:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td></tr><tr><td valign="top"><i class="fa-square-check">:square-check:</i> Yes</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td></tr><tr><td rowspan="2" valign="top">Ignore time not valid</td><td rowspan="2" valign="top">Invalid certificate notAfter or notBefore time</td><td valign="top"><i class="fa-square">:square:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No<br>Card flagged as "card certificate time invalid" status during validation</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No<br>Card flagged as "card certificate time invalid" status during validation</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td></tr><tr><td valign="top"><i class="fa-square-check">:square-check:</i> Yes</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td></tr><tr><td rowspan="2" valign="top">Ignore invalid basic constraints</td><td rowspan="2" valign="top">CA certificate(s) has invalid or missing basic constraints</td><td valign="top"><i class="fa-square">:square:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td></tr><tr><td valign="top"><i class="fa-square-check">:square-check:</i> Yes</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td></tr><tr><td rowspan="2" valign="top">Ignore wrong usage</td><td rowspan="2" valign="top">Invalid keyUsage extension for CA certificate</td><td valign="top"><i class="fa-square">:square:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td></tr><tr><td valign="top"><i class="fa-square-check">:square-check:</i> Yes</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td></tr><tr><td rowspan="2" valign="top">Ignore invalid name</td><td rowspan="2" valign="top">Invalid certificate subject name</td><td valign="top"><i class="fa-square">:square:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td></tr><tr><td valign="top"><i class="fa-square-check">:square-check:</i> Yes</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-xmark" style="color:red;">:circle-xmark:</i> No</td><td valign="top"><i class="fa-circle-check" style="color:green;">:circle-check:</i> Yes</td></tr></tbody></table>
2. If required, check the appropriate checkbox(es) for any faults that are to be ignored.

</details>

<details>

<summary>Certificate Policies tab</summary>

1. Click the **Certificate Policies** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1f49c0c8a24f69a1b7421398671e02e135b68d5d%2Fpivcard_certpoliciestab.png?alt=media)

   This tab allows you to add certificate policies (represented by their corresponding Object Identifiers (OIDs)), to cards issued by a particular agency/agencies, which will be explicitly enforced during periodical certificate validation.
2. Do you want to add Policy OIDs to this PIV Card Type?

   <table><thead><tr><th width="60">If...</th><th>then...</th></tr></thead><tbody><tr><td>no</td><td>go to the next tab.</td></tr><tr><td>yes</td><td><ol><li><p>Click the <strong>Add</strong> button.</p><p>An Add or Modify Policy dialog displays.</p><p><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-cc8f5828c91685c7e8d6df114f7d37d3cc9f2c9f%2Fpivcard_addpolicyoiddialog.png?alt=media" alt=""></p></li><li>Enter the <strong>Object Identifier (OID)</strong> and <strong>Agency code(s)</strong> in the appropriate fields.</li><li>Click the appropriate radio button to indicate if the policy is to be applied to PIV or PIV-I cards.</li><li>Select at least one type of certificate that requires enforcing, by checking the appropriate checkbox(es).</li><li><p>Click the <strong>OK</strong> button.</p><p>The Add or Modify Policy dialog closes.</p></li></ol></td></tr><tr><td colspan="2"><p><strong>Notes:</strong></p><ul><li>The PIV-I column in the grid will display 'Yes' for Policy OIDs that are to be applied to PIV-I cards or 'No' for those to be applied to PIV cards.</li><li>The <strong>Modify</strong> button allows existing Policy OIDs to be modified, and the <strong>Delete</strong> button allows them to be deleted. As soon as the <strong>Apply</strong> button is clicked, the system will automatically attempt to validate the certificates.</li><li>If an error is found during validation an alarm is generated. The <strong>Details</strong> tab of the alarm properties describes the cause of the validation error.</li></ul></td></tr></tbody></table>

</details>

<details>

<summary>Extended Key Usage tab</summary>

1. Click the **Extended Key Usage** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-956c986a52c6f6767bf06f3e604069a00be36e77%2Fpivcard_extendedkeyusagetab.png?alt=media)

   This tab is optional and allows the Operator to select which Extended Key Usages (EKUs) they want to enforce.
2. Do you want to add an EKU?

   <table><thead><tr><th width="60">If...</th><th>then...</th></tr></thead><tbody><tr><td>no</td><td>go to the next tab.</td></tr><tr><td>yes</td><td><ol><li><p>Click the <strong>Add</strong> button.</p><p>An Add or Modify EKU dialog displays.</p><p><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a72d2db023da44b0f1ac472af4a86140cde54296%2Fpivcard_addekudialog.png?alt=media" alt=""></p></li><li><p>Enter the <strong>Extended Key Usage (EKU) OID</strong> (13 digits in the format <em>n.nn.nnn.n.nnn.n.n.n</em>) and <strong>Agency code(s)</strong> (4 digits) in the appropriate fields.</p><p><strong>Note:</strong> If the Extended EKU OID applies to multiple Agency codes, separate the codes with a semi-colon.</p></li><li>Click the appropriate radio button to indicate if the policy is to be applied to PIV or PIV-I cards.</li><li>Select at least one type of certificate that requires enforcing, by checking the appropriate checkbox(es).</li><li><p>Click the <strong>OK</strong> button.</p><p>The Add or Modify EKU dialog closes.</p></li></ol></td></tr><tr><td colspan="2"><p><strong>Notes:</strong></p><ul><li>The PIV-I column in the grid will display 'Yes' for EKU OIDs that are to be applied to PIV-I cards or 'No' for those to be applied to PIV cards.</li><li>The <strong>Modify</strong> button allows existing Policy EKUs to be modified, and the <strong>Delete</strong> button allows them to be deleted. As soon as the <strong>Apply</strong> button is clicked, the system will automatically attempt to validate the certificates.</li><li>If an error is found during validation an alarm is generated. The <strong>Details</strong> tab of the alarm properties describes the cause of the certificate validation error, and the Cardholder's properties (on the <strong>Cards</strong> tab) displays an error:<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-13a9cfaf50fd803c0af6a946bd44ea86a73356f9%2Fpivcard_certificateerror.png?alt=media" alt=""></li></ul></td></tr></tbody></table>

</details>

<details>

<summary>OCSP Responders tab</summary>

1. Click the **OCSP Responders** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b109f4a51816270ed8c31e7dee00e1ef62e8d3a3%2Fpivcard_ocspresponderstab.png?alt=media)

   This tab allows you to add OCSP (Online Certificate Status Protocol) Responders which can be used to validate the status of PIV cards and related certificates.

   **Notes:**

   * The **Modify** button allows existing OCSPs to be modified, and the **Delete** button allows them to be deleted.
   * Every responder that is activated (ticked) will be used for all PIV card certificates in Command Centre. The OSCP Responders will run in list order and the list can be re-ordered by selecting a Responder and using the **Move Up** and **Move Down** buttons to change the priority.
2. Do you want to add an OCSP Address?

   <table><thead><tr><th width="60">If...</th><th>then...</th></tr></thead><tbody><tr><td>no</td><td>go to the next tab.</td></tr><tr><td>yes</td><td><ol><li><p>Click the <strong>Add</strong> button.</p><p>An Add or Modify OCSP dialog displays.</p><p><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-407c44f97de701e8db194cc695252bdb9dc41e31%2Fpivcard_addocspdialog.png?alt=media" alt=""></p></li><li><p>Enter the Universal Resource Identifier (URI) in the <strong>Repeater or Responder URI</strong> field.</p><p><strong>Note:</strong> The URI can be retrieved from the PIV card issuers.</p></li><li>Tick the <strong>Generate nonce</strong> checkbox if you want a nonce (a random set of data) to be included in the OCSP request.</li><li><p>The <strong>Timeout</strong> can be configured so that if a response is not received within the designated time, the request will be terminated.</p><p>(Default = 120. Range = 0 - 1000)</p><p><strong>Note:</strong> Selecting '0' means that it will not timeout.</p></li><li><p>Click the <strong>OK</strong> button.</p><p>The Add or Modify OCSP dialog closes.</p></li></ol></td></tr></tbody></table>
3. The **Use OCSP for certificate validation when available** checkbox determines whether OCSP is the preferred method for certificate validation (ticked), or both CRL and OCSP are used (unticked).

   Tick if you want only OCSP to be used when available.

</details>

<details>

<summary>Registration Options tab</summary>

1. Click the **Registration Options** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6c5b4d5c0c1c602d9f71142d47adcf1afa8b50dd%2F44871.png?alt=media)

   This tab provides a number of options that can be configured for PIV Cardholder registration.
2. If you want to register PIV Cardholders, configure as required:

   1. Select the Image PDF from the drop-down list, which will be used to store the facial image read from PIV cards.
   2. If you want to enable certificate validation at the time of card registration, ensure the **Enable certificate validation** checkbox is ticked, and any other checkboxes in that section to further refine the controls.
   3. If you want fingerprint verification to be part of the PIV Cardholder registration process, ensure the **Enable Fingerprint can and verification** checkbox is ticked.

      **Important:** If you do NOT want to enrol fingerprints you must ensure this checkbox is unticked.

   **Notes:**

   * PIV Cardholder Registration is done in the Command Centre Client. Refer to the "PIV Cardholder Registration Process" in the *Gallagher Command Centre Client User Guide* for the complete process.
   * Tick the **Disable iris image checking** checkbox if you want iris image validation to be disabled while registering a PIV card in Command Centre Client.

</details>

<details>

<summary>Registration Access tab</summary>

1. Click the **Registration Access** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-44216e1130b5c9affc1ef98763b68481a6751252%2Fpivcard_registrationaccesstab.png?alt=media)

   This tab allows you to add default Access Groups to be assigned to PIV Cardholders during registration.
2. Add default Access Groups (if required), as follows:

   1. Click **Manage** from the menu bar, then **Access Groups**.

      The **Access Group** List Window opens.
   2. Drag and drop the required Access Groups into the **Registration Access** tab.
   3. Close the **Access Group** List Window.

   **Note:** If an Access Group contains a 'Required' PDF that does not have a default value, then the cardholder registration will fail with the error message:

   *"Failed to save Cardholder changes.*

   *The cardholder failed to save due to an empty required Personal Data Field".*

   Population of a default value or removal of the 'required' PDF from Access Groups that are added to PIV cardholders during registration is recommended.

</details>

5. Click the **Notes** tab if you want to add a note(s) about the PIV Card Type.

   For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md)*.*
6. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.

### In This Section

* [Setup Certificate Manager](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/piv-card-support/editing-the-piv-card-type/setup-certificate-manager.md)


---

# 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/editing-the-piv-card-type.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.
