> 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/integrated-systems/aperio-integration/configuring-the-aperio-locks-readers/configuring-card-technologies/mifare-desfire-cards.md).

# Configuring MIFARE DESFire cards for use at Aperio Doors

### Introduction

MIFARE® DESFire® cards can interact with doors fitted with Aperio locks within a Command Centre environment.

### Prerequisites

The latest version of the Aperio Programming Application Protocol (PAP) must be installed from the `'Utilities\Aperio'` directory of the Command Centre installation files.

### Procedure

#### Configuring a card type with a non-diversified MIFARE DESFire object

Non-diversified MIFARE DESFire objects can only be added to card types with a facility code that matches the one in your license. More than one non-diversified MIFARE DESFire object can be added to a card layout.

1. Configure a card layout with a non-diversified MIFARE DESFire object in Configuration Client.

   See [Adding a Non-diversified MIFARE DESFire object](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/designing-card-layouts/working-with-objects/card-type-objects/adding-a-non-diversified-mifare-desfire-object.md) for the procedure.

#### Applying the MIFARE DESFire configuration to an Aperio Door/Lock

Once you have imported a configuration, you will need to apply the MIFARE DESFire configuration to a lock in Aperio PAP.

2. **Right click** the lock and select **Lock/sensor** > **Configure…**

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

   The Configure Lock/sensor screen opens.
3. Select **MIFARE DESFire** from the drop-down list and click **Add...**

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

   The MIFARE DESFire Configuration dialog displays.
4. Change the **RFID Card Type** from ‘DESFire UID’ to ‘DESFire’.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-ce970257cd58e8521b43329d48b4e4baf11b294d%2Fmifaredesfireconfigurationdialog.png?alt=media)
5. Convert the **Application ID** of the non-diversified MIFARE DESFire object (on the card layout) from hexadecimal to decimal digits.

   **Note:** A programmer mode calculator can be used for this.
6. Enter the decimal number in the **Application Id** field.

   **For example**: ABC123 (Hex) = 11256099 (Decimal).
7. Configure the other fields as follows:

   <table><thead><tr><th width="210">Field</th><th>Enter...</th></tr></thead><tbody><tr><td>File Identity</td><td>0</td></tr><tr><td>File Start Position</td><td>0</td></tr><tr><td>Length to read in File</td><td>16 (the length of the non-diversified MIFARE DESFire object properties)</td></tr><tr><td>File Data Protection Level</td><td>Plain</td></tr><tr><td>Key Type</td><td>AES-128</td></tr><tr><td>Key</td><td>the <strong>AES Key</strong> from the non-diversified MIFARE DESFire object properties, (i.e. 32 hexadecimal characters)</td></tr><tr><td>Key Number</td><td>0</td></tr></tbody></table>

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-92d48b4a5e249760d6d16c7d243eeaf6f40015ca%2Fmifaredesfireobjectconfiguration.png?alt=media)
8. Click the **OK** button.

   The MIFARE DESFire Configuration dialog closes and you are returned to the Configure Lock/Sensor screen.
9. Click the **Next** button on each screen until you get to the ‘Device Update’ screen, where you are prompted to badge a card at the sensor to upload the configuration at each door.

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

   **Note:** We recommend that you save the configuration at this point in order to more easily apply the configuration to other locks.
10. Click **Apply** and badge the type of card the lock was previously configured to, in order to upload the new configuration to the lock.
11. If the lock is updated successfully, the following screen displays:

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

    See [Locks failing to update](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/aperio-integration/configuring-the-aperio-locks-readers/configuring-card-technologies/locks-failing-to-update.md) fro details of what happens of the lock configuration fails.


---

# 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/integrated-systems/aperio-integration/configuring-the-aperio-locks-readers/configuring-card-technologies/mifare-desfire-cards.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.
