> 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/products/cc-software/troubleshoot/command-centre-errors/command-centre-errors-authentication-f.md).

# Authentication Failed with Supplied Key(s)

[Command Centre - Errors](/knowledge-hub/products/cc-software/troubleshoot/command-centre-errors.md) › Authentication Failed with Supplied Key(s)

**Error:** "Authentication failed with supplied key(s)."

Cards have been encoded with different keys than the ones in the system. You cannot encode or read card numbers from MIFARE DESFire cards because they are encoded with a different site key.

![Error: authentication failed with supplied keys](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-e482c5a6a5082a00e0f718a5712d398a44f06799%2FSECHUB-CCS-ERR-AUTH-FAILED-KEY-01.jpg?alt=media)

## Resolution

Import the site key that the cards are encoded with, or get new cards.

## A simple scenario

1. A Channel Partner installed Command Centre.
2. Generated a new MIFARE Key Seed (SSK).
3. Encoded cards.
4. At some stage uninstalled and re-installed Command Centre **without backing up the SSK**.

The site SSK has changed, so they can no longer re-encode the original cards because the keys do not match.


---

# 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/products/cc-software/troubleshoot/command-centre-errors/command-centre-errors-authentication-f.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.