> 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/getting-started/fido2-credentials.md).

# FIDO2 Credentials

This feature provides the ability to use open standard (FIDO2) authentication factors for operator/cardholder authentication at Command Centre logon.

**Note:** FIDO2 Credentials are only supported from Windows 10, version 1903.

**Single-factor authentication** is when a FIDO2 token has no biometrics, (i.e. fingerprint) or PIN associated with it.

**Multi-factor authentication** means using two or more of the following:

* Token or card
* PIN and/or biometric

It is a requirement of the 2019 CAPSS standard that admin users must be verified with multi-factor when logging onto the system.

This feature has been tested using the following FIDO2 Credential tokens:

* Feitian BioPass (K27)
* Feitian BioPass (K33)
* Feitian Fingerprint Card
* eWBM Goldengate
* GoTrust Idem Key
* Yubico Yubikey 5 NFC
* TRUSTKEY B210H

<details>

<summary>Enrolling FIDO2 Credential against Cardholder</summary>

### Introduction

This topic describes the process for enrolling FIDO2 Credentials against cardholders. Multiple FIDO2 Credential tokens can be registered against a user in Command Centre, (e.g. further tokens can be issued if a cardholder loses their token).

Operators require one of the following operator privileges to enrol a FIDO2 Credential against a cardholder:

* Advanced User
* Add Card or Credential
* Create and Edit Cardholders
* Create Cardholders
* Edit Cardholders
* Edit Site

### Prerequisite

Before proceeding with this procedure, a FIDO2 token must be set up using the manufacturer’s instructions.

### Procedure

1. Select the **Viewers** tab on the Command Centre title bar, then click **Cardholder Viewer** on the toolbar.

   The Cardholder Viewer opens.
2. Locate the cardholder you want to enrol a FIDO2 Credential against.

   See [Searching for Cardholders](https://help.security.gallagher.com/knowledge-hub/command-centre-client/using-command-centre/working-with-viewers/cardholder-viewer/simple-searching-for-cardholders.md) for the procedure if required.
3. On the Cardholder Cards tile, click the **Assign Card** button.

   The Assign Card pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-423cc22d3d62bcdb9e4a034986f268ae1a3663d9%2Ffido2_assigncardpopup.png?alt=media)
4. Select "FIDO2 Credential" from the **Card Type** drop-down list and select the appropriate **State**.

   **Note:** FIDO2 Credentials are only supported from Windows 10, version 1903. If your version of Windows is not supported the following message will display:

   *\* FIDO2 is not supported on this version of Windows*.
5. Enter a description to allow easy identification of the token in the **Description** field (limited to 60 characters).

   **Note:** The Description field is mandatory and will display in the "Number" column of the Cardholder Cards tile.
6. Click the **Enrol Credential** button.

   Windows Security prompts for the FIDO2 token.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-f149452ca758197445d2b38b173e2d5f3fa79fd6%2Ffido2_enrolling_touchsecuritykeyscrn.png?alt=media)
7. Insert the FIDO2 token.

   Verification data is passed to the server.
8. Does the system verify the token?

   If **yes**, a message displays indicating that the credential is successfully enrolled against the cardholder.

   If **no**, a message displays indicating the reason why enrolment is denied.
9. Click the **OK** button.

   The Assign Card pop-up closes and if the credential enrolment was successful, the credential is added against the cardholder.

   Validation will be unsuccessful if an invalid token has been used or the root certificate is invalid. When credentials fail to enrol, an error message will display, e.g.

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

   **Note**: In the case of the FIDO2 MDS Blob is invalid error above, refer to Step 3 of the *"Card Security"* topic in the Configuration Client online help for *Updating the FIDO2 MDS Root Certificate* instructions.

   Expired FIDO2 MDS Blobs normally get updated automatically through the internet, however if the site has no internet to update an expired Blob, the following error will display:

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

   The Blob cannot be updated through Command Centre, therefore manually download it from <https://fidoalliance.org/> and place it into the `'C:\ProgramData\Gallagher\FIDO2'` directory where Command Centre will then utilise it for the next token enrollment.

### Hints

{% hint style="info" %}
**Reverting to saved after successful enrolment**

If a user successfully enrols a credential but then clicks the **Revert** to Saved button in the main window, the standard message will appear about having unsaved changes but will not detail the state of the enrolled/unenrolled credential.
{% endhint %}

{% hint style="info" %}
**Cancelling enrolment**

Should a user wish to cancel a credential after enrolling it, (e.g. they enrolled the wrong token), if they click the **Cancel** button a warning message displays to the effect of:

*"Credential has been enrolled to the FIDO2 device and should be manually removed."*

Once a credential is enrolled to a token, it is not possible to select and remove a specific credential from any of the tokens that this feature has been tested on (see [FIDO2 Credentials](https://help.security.gallagher.com/knowledge-hub/command-centre-client/getting-started/fido2-credentials.md) for the list of tokens). A user would usually have to be reset, which means they would lose all the credentials on their token. If they do cancel, then they will have to use a third-party application to remove the credential from the device.

**Note:** It isn’t necessary for a credential be removed from a token, as most tokens can hold 100+ credentials. It would just become a redundant credential that would never be used.
{% endhint %}

</details>

<details>

<summary>Enforcing FIDO2 Multi-factor Logon</summary>

### Introduction

Enforcing FIDO2 Multi-factor logon is configured via Operator Groups. Therefore, all cardholders that are required to logon to Command Centre using a FIDO2 authenticator must be members of an Operator Group that has FIDO2 Multi-factor logon enforced.

Operators require one of the following operator privileges to enforce FIDO2 Multi-factor logon:

* Advanced User
* Edit Site and Edit Operators

### Prerequisite

Before proceeding with this procedure FIDO2 Credentials need to be enrolled against cardholders. See [Enrolling FIDO2 Credential against Cardholder](https://help.security.gallagher.com/knowledge-hub/command-centre-client/getting-started/fido2-credentials/enrolling-fido2-credential-against-cardholder.md) for the procedure.

### Procedure

1. Select the **Administration** tab on the Command Centre title bar, and then click the **Operator Groups** button on the toolbar.

   The Operator Groups Viewer opens.
2. Click on the Operator Group that you want to enforce FIDO2 Multi-factor logon for.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-36c256109d5825e0ded33088861e1a341fb4de7b%2Ffido2_enforcemultifactor.png?alt=media)
3. Check the **Enforce FIDO2 multi-factor logon** checkbox.

   **Note:** This checkbox will be disabled (greyed out) if FIDO2 Credentials have not been enrolled against cardholders.
4. Click the **Save** button.

</details>

<details>

<summary>Creating a new FIDO2 Credential State Set</summary>

Perform the following procedure to create a new FIDO2 Credential State Set:

1. Click the **New Card State Set** button on the Viewer Navigation Panel, and then **FIDO2 Credential State Set**.

   The new FIDO2 Credential State Set is added to the Viewer Navigation Panel, and the Card State Configuration pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-82d954a65e9ce8d17ece6481469c0460f4d1a43a%2Ffido2_cardstateconfigurationpopup.png?alt=media)
2. If you want to replace the default name the system has given the FIDO2 Credential State Set, enter a new name in the **Name** field (limited to 60 characters).
3. If required, enter a logical **Description** (limited to 200 characters).
4. The **Division** button defaults to the name of the last Division in which the Operator created a Command Centre item, regardless of whether it was created in Configuration Client or via Command Centre Client.

   If this is not the appropriate Division for this Card State Set, select a Division as follows:

   1. Click the **Division** button.

      A browse tool displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-7b199073d021ca11902823b748c96d639d5d5f0f%2Fselectdivision_browsetool.png?alt=media)
   2. Select the appropriate Division.
   3. Click the **OK** button.

      The pop-up closes and the button changes to the name of the Division you selected.

      **Note:** If you have not set up Divisions yet, you can add these to your Card State Set at a later stage.
5. Click the **Close** button.

   The Card State Configuration pop-up closes.

   There is one tab, (i.e. **Card States** ).

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-4c26df4d558ee4ae241537e48613e613fc3a0db0%2Ffido2_cardstatestab.png?alt=media)
6. Change the **Initial Card State** if required, by selecting another one from the drop-down list.
7. Add and remove Card State(s) as required for this Card State Set. See [Adding States to a Card State Set](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/card-states/adding-states-to-a-card-state-set.md) and [Removing States from a Card State Set](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/card-states/removing-states-from-a-card-state-set.md) for the procedure.
8. Indicate whether a custom card state is available for selection on the Cardholder Cards tile.

   States available for selection are indicated by a "tick" and are made by clicking in the checkbox in the **Available for use** column.

   **Note:** By default, all custom card states are available for selection.
9. Change any of the custom card states to **Permanently Disabled** if required.

   **Note:** The "Active" and "Disabled (manually)" states cannot have their attributes changed, (i.e. they are always available and cannot be made a permanently disabled state).
10. If you want to record any note(s) about the Card State Set, click the **History/Notes** tab.

    Refer to [History/Notes tab](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/history-notes-tab.md) for further detail.
11. Click the **Save** button.

    A new Card State Set has been created.

</details>


---

# 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/getting-started/fido2-credentials.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.
