> 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/introduction-to-command-centre/getting-started/logon/logon-with-fido2-credentials.md).

# Logon with FIDO2 Credentials

### Introduction

Cardholders that have FIDO2 Credentials enrolled against them can log on or off designated Command Centre workstations with a FIDO2 authenticator.

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

Configuration of FIDO2 Credentials is performed in Command Centre Client. For further information refer to the "FIDO2 Credentials" section in the *Command Centre Client Help file.*

### Procedure

1. Open Configuration Client by either:
   * double-clicking the **Configuration Client** icon on your Desktop, OR
   * from the **Start** menu, click **All Programs** > **Gallagher** > **Configuration Client**.
2. Select "FIDO2 Authentication" from the **Logon Method** drop-down list.

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

   Once "FIDO2 Authentication" is selected, the **Password** field is disabled (greyed out).
3. Type your **Logon Name**.
4. Click the **Logon** button.

   The username is sent to the server, and Windows prompts for the FIDO2 token.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-3e2928ba8646c51763a6e54bccdcd92e035e44a2%2Ffido2_inserttokenscrn.png?alt=media)
5. Insert the FIDO2 token (and biometric/PIN if applicable).

   Verification data is passed to the server, and you are prompted to ‘touch’ the token to verify there is someone there.

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

   **Note:** The system will time out if no action is taken within 60 seconds.
6. Does the system verify the token?

   If **yes**, you are logged into Command Centre Configuration Client.

   If **no**, a message displays indicating the reason why access is denied.


---

# 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/introduction-to-command-centre/getting-started/logon/logon-with-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.
