> 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/command-centre-client/using-command-centre/licensable-features/piv-card-support/piv-cardholder-registration-process.md).

# PIV Cardholder Registration Process

### Introduction

The PIV Cardholder Registration process is only available to sites that are licensed for Personal Identity Verification (PIV). The registration process supports both PIV and PIV-I cards.

**Note:** Expired and revoked cards cannot be enrolled in Command Centre.

During PIV Cardholder Registration, various information is read from a card and stored in Command Centre. As part of this, an Image Personal Data Field (PDF) is needed to store the facial image read from the card. Although not necessary, be aware that if this isn't done, facial images read from cards will not be stored and will not be available later for viewing.

Gallagher recommend:

* **To store images:** Create an Image PDF and link it to the PIV Card Type. Follow "Creating an Image PDF" (Step 1 below).
* **To view images in the Cardholder Viewer:** Assign this Image PDF and Cardholder to the same Access Group. Follow "Assigning Cardholders to Access Group" (Step 19 below) after the cardholder is registered.

### Procedure

To register PIV Cardholders, perform the following procedures in the order specified:

Creating an Image PDF

1. Create an Image Personal Data Field (PDF) in the Command Centre Client, and assign the Image PDF to an Access Group.

   See [Creating a new Personal Data Field](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/personal-data-fields/creating-a-new-personal-data-field.md) for the procedure.

### Configuring Registration Options on the PIV Card Type

Operators require the "Configure Site" privilege in the appropriate division to link an Image Personal Data Field to the PIV card type, set certificate validation options and enable fingerprint verification. This procedure is performed in the Configuration Client, as follows:

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

   The Card Type Master List Window opens with the "PIV Card" appearing by default.
3. **Right click** on the "PIV Card" and select **Properties**.

   By default the **General** tab displays.
4. Click the Registration Options tab.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-93389f62fcdc7fe774f029989330617fbc8c3f38%2F44906.png?alt=media)
5. Configure the PIV Cardholder registration options 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 require certificate validation, check the **Enable certificate validation** checkbox, and then check each of the options you want to be enforced at the time of PIV Cardholder registration.

      <table><thead><tr><th width="210">Option</th><th>Description</th></tr></thead><tbody><tr><td>Validate optional certificates</td><td>If checked, the two optional certificates, (i.e. Key Management Certificate and Digital Signature Certificate) will be validated.</td></tr><tr><td>Validate the content signing certificate</td><td>If unchecked, the content signing certificate will not be validated. This is used to digitally sign the PIV objects and is issued to the issuer of the card and not for the cardholder.<br>If you choose to trust this issuer then you may be happy to not validate this certificate.</td></tr><tr><td>Ignore end-entity certificate revocation unknown</td><td>If checked you are allowing entity certificate with unknown revocation status to be enrolled. This may be of benefit when experiencing network problems or the CA server is down, to allow enrolment immediately.</td></tr><tr><td>Ignore certificate authority revocation unknown</td><td>If checked you are allowing intermediate certificate with unknown revocation status to be enrolled. This may be of benefit when experiencing network problems or the CA server is down, to allow enrolment immediately.</td></tr><tr><td>Enforce CHUID expiration nesting</td><td>If checked, all certificate expiry dates need to be on or before (not after) CHUID expiry date.</td></tr><tr><td>Ignore time not valid</td><td>If checked, validation will ignore expired certificates and certificates not yet active.</td></tr></tbody></table>
   3. If you require biometric verification, check each of the **Enable Biometric Verification** options you want to be enforced at the time of PIV Cardholder registration.

      <table><thead><tr><th width="283">Option</th><th>Description</th></tr></thead><tbody><tr><td>Ignore biometric object time not valid</td><td>If checked, verification will ignore biometric objects not yet active.</td></tr><tr><td>Enable Fingerprint scan and verification</td><td>If checked, fingerprint verification will be part of the PIV Cardholder registration process.</td></tr><tr><td>Disable iris image checking</td><td>If checked, iris image validation will be disabled while registering the PIV card.</td></tr></tbody></table>
6. Click the **OK** button to exit and save your changes.

### Registering a PIV Cardholder

Register PIV Cardholders in the Command Centre Client, as follows:

7. Click the **Cardholder Viewer** button on the Command Centre toolbar.

   The Cardholder Viewer opens.
8. Select the cardholder in the Navigation Panel.
9. Click the **Register PIV Cardholder** button.

   **Note:** The **Register PIV Cardholder** button will only be active if you have the privileges to create and edit a cardholder.

   If a card has NOT been inserted in the reader, the Insert PIV card screen of the Register PIV Cardholder pop-up displays. If this screen does not display, go to Step 12.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-c36426b62a1857178d264ad60fb8df2c89cfd807%2Fregisterpivcardholder_popup1.png?alt=media)
10. Select the **Registration Reader** from the drop-down list, and insert a card into the reader.
11. If a PIV card is inserted in the reader, the Enter PIN screen of the Register PIV Cardholder pop-up displays.

    ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-cd2aa1b65cec3060198cda1fa571646addbb0b40%2Fregisterpivcardholder_popup2.png?alt=media)
12. Get the Cardholder to enter their PIN.

    **Note:** The PIN will display as a row of asterisks (\*) as it is entered.
13. Click the **Next** button.

    Does the Scan Fingerprint screen of the Register PIV Cardholder pop-up display?

    ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-951254943aa1d9124346da81854a1a8db7b405ed%2Fregisterpivcardholder_popup5.png?alt=media)

    <table><thead><tr><th width="126">If...</th><th>then...</th></tr></thead><tbody><tr><td>no,</td><td>go to Step 14.</td></tr><tr><td>yes,</td><td><ol><li>Select the available (installed) reader from the <strong>Fingerprint Reader</strong> drop-down list.<br>A red light activates on the fingerprint reader indicating that it is ready to scan the Cardholders finger.</li><li>Get the Cardholder to place their finger on the fingerprint reader.<br>The fingerprint captured is verified against the fingerprint template existing on the card.</li></ol></td></tr></tbody></table>
14. As the card data is being registered, progress is indicated to the operator on the Retrieving card information… screen.

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

    Once registration has completed successfully, the cardholder details display.

    ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-51747050b1d1b06c810290684b352d1a140b301f%2Fregisterpivcardholder_popup4.png?alt=media)

    **Note:** The **Name**, **Employee Affiliation** and **CHUID Expiry Date** are non-editable fields as read from the card. The **First Name**, **Last Name** and **Division** are editable fields representing the details that will exist in the Command Centre database when saved.
15. Edit the **Name** and/or **Division** fields if necessary.
16. Click the **Save** button.

    The following occurs:

    * The cardholder details appear in the Cardholder Viewer, (i.e. the cardholder is selected in the Navigation Panel and applicable tiles are populated and visible), and
    * The Register PIV Cardholder pop-up returns to the Insert PIV card screen.
17. Remove the PIV card from the reader.
18. Repeat Steps 10 - 16 for each subsequent PIV cardholder you wish to register.
19. When all registrations are complete, click the **Cancel** button to close the Register PIV Cardholder pop-up and return to the Cardholder Viewer.

### Assigning Cardholders to Access Group

If you want the image to display in the Cardholder Images tile, perform the following step:

20. Assign each of the PIV cardholders the Access Group that has the Image PDF assigned to it (from Step 1).

    **Note:** There are a number of methods that can be used to assign the Access Group to cardholders, (e.g. from the Cardholder Access Groups tile in the Cardholder Viewer, from Access Groups on the **Administration** tab).

### Hint

{% hint style="info" %}
**When a card already exists**

If a card with the same FASC-N as an existing card in Command Centre, is registered or re-registered in Command Centre, the card will 'replace' the existing card record for the same cardholder. If the name of the cardholder has been changed in the database at or since the earlier card registration then the updated First Name and/or Last Name will be displayed during registration thus reflecting the names held in the database. These fields can be further changed if required during this (re)registration.
{% endhint %}


---

# 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/command-centre-client/using-command-centre/licensable-features/piv-card-support/piv-cardholder-registration-process.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.
