> 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/salto-lock-interface/command-centre-site-configuration/encoding-cards/adding-salto-mifare-objects-to-a-card-layout.md).

# Adding Salto MIFARE objects to a card layout

### Introduction

Salto MIFARE objects can be added to a Card Type, allowing you to encode Salto data onto MIFARE® card technologies as follows:

<table><thead><tr><th width="168">Salto Objects</th><th>Allows you to encode Salto data on...</th></tr></thead><tbody><tr><td>Salto MIFARE Classic</td><td>MIFARE Classic® cards.</td></tr><tr><td>Salto DESFire</td><td>MIFARE® DESFire® EV1 to EV3 (AES) cards.</td></tr></tbody></table>

**Notes:**

* A site can use all three card technologies, (i.e. MIFARE DESFire EV1 to EV3 and MIFARE Classic) con-currently, when using Salto readers that support these card technologies.
* Salto and Morpho FVP objects on the same card layout is not supported.
* Events from Salto offline readers are stored on the card. The older events are transferred from the card to the Salto server when the card is presented at a Salto wired reader. Using the default configuration (of 11 sectors) approximately 24 events can be stored on a card.

  **Note:** Of the 11 sectors approximately 5 sectors are dedicated to access, (i.e. they cannot store events).

### Procedure

This procedure describes how to add a Salto MIFARE object, (i.e. Salto MIFARE Classic or Salto MIFARE DESFire), to a card layout.

1. Click **Configure** from the menu bar, then **Card Types**.

   The **Card Type** List Window opens.
2. **Right click** on the required card, and select **Edit Card Layout**.

   The **Card Editor** window displays.
3. Select the Salto MIFARE object type you want to add. Either:

   * **New Salto MIFARE Classic Object** ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1d9dfce7bd5103a4cc01520c413289fac1a9735c%2Fsalto_1.png?alt=media)
   * **New Salto MIFARE DESFire Object** ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e47a83160b029b2b41cd09211eaf113d5ddd4c94%2Fsalto_3.png?alt=media)

   An object box displays with placeholders around it.

   **Notes:**

   * These options are only available if your license contains one or more Salto doors.
   * The size of the object box can be expanded if necessary. See [Expanding an Object Box](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/expanding-an-object-box.md) for procedure.
4. **Right click** on the Salto object, then click **Properties** from the drop-down menu.

   What Salto object type did you select?

   <table><thead><tr><th width="198">If...</th><th>then the...</th></tr></thead><tbody><tr><td>Salto MIFARE Classic,</td><td>Salto MIFARE Properties dialog box displays:<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-100a45fea3c77473ae5e94c3a5c3da456f2f4156%2Fsalto_2.png?alt=media" alt=""></td></tr><tr><td>Salto MIFARE DESFire,</td><td>Salto DESFire Properties dialog box displays:<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-de52e0721fb1958407ca80c3860e4bef647ef85b%2Fsalto_desfireproperties.png?alt=media" alt=""><br>If your site is licensed for Bureau Encoding, the Salto DESFire Properties dialog box will have an additional Automatic Key Assignment Settings section on it:<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-af9ae8c5ef43996f3782c8beef3334fecdeacd7f%2F44863.png?alt=media" alt=""></td></tr></tbody></table>
5. Configure the Salto MIFARE properties as required:

   <table><thead><tr><th width="154">Salto object type</th><th width="143">Option</th><th>Description</th></tr></thead><tbody><tr><td rowspan="2">Both</td><td>Write Events on Cards</td><td><p>Indication of whether to write events on the card or not. (Default = Checked).</p><p>If you change this setting, any cards that have been previously encoded will need to be re-encoded. Otherwise a long beep is heard from the wired reader after the card grants access, and if the setting is being turned on, then it will not take effect until re-encoding the card.</p><p><strong>Note:</strong> Salto offline doors also need to have 'Audit on keys' enabled.</p></td></tr><tr><td>Salto Server</td><td>If your site supports multiple Salto Servers, specify the Salto Server data to be encoded from the drop-down list.</td></tr><tr><td rowspan="2">Salto MIFARE Classic</td><td>MIFARE start sector</td><td>This field must be between 1 and 11, or 17 and 27.</td></tr><tr><td>Number of sectors</td><td><p>This field must be between 5 and 15, and the "MIFARE start sector" plus the "Number of sectors" must be less than or equal to 16, or less than or equal to 32 if "MIFARE start sector" is greater than 16.</p><p><strong>Note:</strong> Approximately 10 events are stored per sector, and approximately 5 sectors are dedicated to access, (i.e. they cannot store events).</p></td></tr><tr><td rowspan="2">Salto MIFARE DESFire</td><td>Salto Application File Size</td><td><p>The file size (in bytes) for this Salto application.</p><p>(Range 320 - 7200 bytes. Default 512 bytes)</p><p>Reducing the file size will decrease the number of card events (from Salto wireless readers) that can be stored on the card. Increasing the file size will limit the available space for other applications on the card. Supported card sizes are 2K, 4K and 8K.</p><p><strong>Note:</strong> The default file size of 512 bytes will store approximately 28 card events on the card.</p></td></tr><tr><td>Key Assignment Encoding</td><td>This card needs to be created on your third party system (non-Salto) with the checkbox ticked. You do not need to have a card type on your Command Centre Salto System with this checked. (Default = Unchecked)</td></tr><tr><td>Salto MIFARE DESFire, if your site is licensed for Bureau Encoding</td><td>Automatic Key Assignment Settings</td><td><p>This section provides the ability to override the key assignment settings, and will cause the encoding to do "In-Memory Code" even if set to CSN. It allows operators to encode for different sites without going back to the Salto Server properties between batch encoding runs.</p><ul><li>Clicking the Generate button creates an <strong>App Key</strong>.</li><li>The <strong>App ID</strong> field must be a non-zero hexadecimal value exactly six characters long.</li></ul></td></tr></tbody></table>

   **Note:** The **Default** button allows you to reset the Salto MIFARE properties back to the default settings.
6. If you want to configure common encoding properties, click the **Edit Common Properties** button.

   The Common Card Encoding Properties dialog box displays.
7. If not already selected, select the appropriate card technology, (i.e. MIFARE Classic or MIFARE DESFire), from the **MIFARE Encoding Technology** drop-down list.

   The fields that populate the dialog box depends on the card technology selected, (e.g. the following screen example demonstrates how it will look when **MIFARE Classic** is selected).

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

   Regardless of the card technology selected, by default the **Gallagher Issued** checkbox is enabled (ticked), which means that when you configure the MIFARE object on a card layout, all other configuration options are disabled.
8. To alter the MIFARE properties, uncheck the **Gallagher Issued** checkbox.

   All the fields become enabled.
9. Configure the MIFARE properties as required:

   <table><thead><tr><th width="150">Salto object type</th><th width="132">Option</th><th>Description</th></tr></thead><tbody><tr><td>Salto MIFARE Classic</td><td>Remove old Gallagher data</td><td><p>This checkbox allows you to either leave the old Gallagher data on the card or remove it.</p><p><strong>Notes:</strong></p><ul><li>Removing the old Gallagher data will only succeed if the old card data was encoded with the same MIFARE DESFire key seed and same facility code as this Card Type.</li><li>If you write to the same sector as previously, the Gallagher data is removed and re-written if the facility code of the sector is the same facility code as this Card Type.</li></ul></td></tr><tr><td></td><td>Unlock Key (Application Directories)</td><td><p>This field allows you to access Sector 0 in the Application Directory.</p><p>For example, a third parties MAD write key should be entered in this field if the MAD has been locked by the other party and hence the card manufacturer’s key or Gallagher unlock key won’t work.</p><p>The key must consist of 32 hexadecimal digits (0-9 and A-F).</p></td></tr><tr><td></td><td>Fail encoding if the application directory update fails</td><td><p>The MIFARE Application Directory (MAD) is the directory of all the sectors on the card.</p><p>By default this checkbox is enabled (ticked), which means if the MAD can be unlocked, then it will always be updated with this information. If you choose to encode cards with the MAD or CAD locked, uncheck this checkbox.</p></td></tr><tr><td>Salto MIFARE DESFire</td><td>Use card master key</td><td><p>If the card has been initialised by a third party using a card master key, you will need to enter the third parties master key in this field, in order to encode data onto the card.</p><p>When checked, the <strong>Type</strong> drop-down box and the <strong>Card Master Key</strong> field are enabled.</p></td></tr><tr><td></td><td>Type</td><td>This drop-down box lists the values "AES", "2K3DES" or "3K3DES". This allows selection of the type of encryption used for the Card Master Key.</td></tr><tr><td></td><td>Card Master Key</td><td><p>This field must have either 32 hexadecimal characters for AES or 2K3DES encryption types, or 48 hexadecimal characters for 3K3DES encryption type.</p><p>Hexadecimal character validation occurs when the <strong>OK</strong> button is clicked.</p></td></tr><tr><td></td><td>Default Application Key</td><td><p>The Default Application Key is required when encoding cards that have been personalised by a third party site. This is the key that will allow the Gallagher applications to be created on the card.</p><p>This field must have 48 hexadecimal characters. If the third party key provided is only 32 characters in length, this field must be padded out to make a 48 hexidecimal character key with the additional characters added to the end of the key. Hexadecimal character validation occurs when the <strong>OK</strong> button is clicked.</p></td></tr></tbody></table>

   **Note:** The **Default** button allows you to reset the MIFARE Classic properties back to the default settings.
10. Click the **OK** button to save the MIFARE Classic encoding properties.

    The Common Card Encoding Properties dialog box closes.
11. Click the **OK** button to save the Salto MIFARE encoding properties.

    The Salto MIFARE Properties dialog box closes.


---

# 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/salto-lock-interface/command-centre-site-configuration/encoding-cards/adding-salto-mifare-objects-to-a-card-layout.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.
