> 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-cards-in-command-centre.md).

# PIV cards in Command Centre

There are a number of differences between PIV cards and other card types, and how they appear in either of the Command Centre clients, (i.e. Configuration Client and Command Centre Client).

When PIV card types appear on the 'Cardholder Cards Tile' in Command Centre Client, or on the **Cards** tab of a Cardholders properties in Configuration Client, it is important to be aware of the following differences with other card types:

* The **Issue** Level is "read-only" for PIV cards.
* Activation ( **From** ) and Expiry ( **Until** ) Dates/Times are not enabled, as they are read directly from the PIV card itself during enrolment and registration.

  **Note:** The **Until** Time is Midnight UTC and will show as the local workstation time, (i.e. New Zealand will be 12:00).
* When assigning a card to a cardholder, the PIV Card Type does not appear in the **Card Type** drop-down list, as PIV cards cannot be manually assigned.
* None of the encoding options are enabled for PIV cards.
* When the Validation server is unable to be contacted, the cardholder card status shows as 'Certificate status unknown', (i.e. in the **Status** column in the Command Centre Client, or to the right of the **Card Enabled** checkbox in the Configuration Client). PIV cards with this status remain in an 'active' state and can still be used to gain access where appropriate.
* In Command Centre Client, the **Last Validation Time** column only appears if a cardholder has at least one PIV card, and will be populated with the last successful time that the active PIV card certificates have been validated.
* In Command Centre Client, a random or user generated PIN number can be securely hashed and stored in the database for each PIV card record.

  **Note:** The PIV card will not be read at the time of setting the PIN.

  For any selected PIV card that an operator has the privilege to edit, and has been configured to ‘Use PINs’ (in Configuration Client), the Cardholder Cards tile will display an enabled **Assign PIN** button to launch the Assign PIN window.

  **Note:** When the operator only has the privilege to view the card, the **Assign PIN** button will be disabled.

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

  **Assigning PINs**

  1. Click the **Assign PIN** button.\
     The Assign PIN pop-up displays.<br>

     ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-78169979a4f3a83ebe8f13f5835bae8f30ecae29%2Fassignpin_popup.png?alt=media)
  2. Either:
     * Manually type a PIN number into the first **User PIN** field, and then confirm it by repeating it in the second **User PIN** field, OR
     * Click the **Generate PIN** button to automatically generate a random PIN.\
       **Note:** Generated PINs will only display while the Assign PIN window is open. Once closed, there will be no way of re-viewing the PIN number since the PIN itself is not stored. Generated PINs will be of length equal to the minimum PIN length set against the PIV Card type.\
       \
       **Note:** The system prevents PINs with 3 consecutive or 3 repeating numbers from being either manually entered or automatically generated.
  3. Click the **OK** button.\
     The Assign PIN pop-up closes.
  4. Click the **Save** button.

### Searching for PIV cards in Command Centre Client

**Simple Searching**

When performing a simple search for a PIV card, by card number, the numbers entered in the **Search** field must match the Federal Agency Smart Credential Number (FASC-N) PIV card format, including the dashes, (i.e. 4-4-6 digits. With the first 4 digits being the Agency code, the next four digits the System code and the last six digits the Credential number).

For example, if there was a PIV card number 1234-5678-987654, and 123456\* was entered in the **Search** field, the card would not be found. However, if 1234-56\* was entered, it would appear in the search results.

**Advanced Searching**

When performing an advanced search for PIV cards, there are a number of conditions available to help define your search. When you click the **Insert Condition** button on the 'Advanced Search Rule Definition' pop-up, the following options are available:

* From the Condition Type drop-down list you can select either **Cardholder has Card issued by Certification Authority (PIV)** or **Cardholder has Card not validated during past 24 hours (PIV)**.

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

  The **Cardholder has Card issued by Certification Authority (PIV)** option can:

  * find all cardholders that have PIV cards issued by a particular Certification Authority.
  * combine with a revoked search to find all revoked cards for a particular Certification Authority.
  * combine with other search filter criteria to find a subset of cards issued by a particular Certification Authority.

  The **Cardholder has Card not validated during past 24 hours (PIV)** option returns cardholder records that have PIV cards that have failed to have all certificates validated in the past 24 hours, due to an inability of Command Centre to contact the Validation Authority.

  **Note:** Newly created cardholder records will not be returned until a minimum 24 hours after enrolment.
* By selecting the Condition Type "Cardholder Card Status" from the drop-down list, you can search for PIV cards of either a **Revoked** or **Not Trusted** status.

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


---

# 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-cards-in-command-centre.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.
