To accelerate cardholder creation and prevent typos when copying a cardholder onto
another system, you can encode cardholder information on a MIFARE DESFire card. When assigning
the card to a new cardholder on the other system using a STid reader, the cardholder fields are
automatically populated by the values encoded on the card.
Before you begin
Ensure the following:
What you should know
- Cardholder information is encoded on MIFARE DESFire cards by configuring custom string
files in MIFARE DESFire configurations. The information defined in the custom strings is
then retrieved from an existing cardholder. Each custom string file contains at least one
custom string that defines information about the cardholder from fields such as first
name, email address, cardholder custom fields, manually entered values, and so on.
- Each MIFARE DESFire configuration defines one application.
- You can store up to 28 applications on a DESFire EV1 card, or as many applications
as there is space on EV2 and EV3 cards.
- An application can be empty (for future use) or contain up to 32 files.
- A file can be empty (for future use) or contain a credential or a custom
string.
- Security Center 5.11.3.0 or later is required to perform this task.
Procedure
-
From the Config Tool homepage, open the
MIFARE DESFire configuration task.
-
From the MIFARE DESFire configuration list, and then click
Add an item ().
-
In the Badge configuration section, enter a
Configuration name.
-
Select the Card encoding check box.
-
Add a custom string file to the application:
-
At the bottom of the File selection section, click
Add an item ().
-
(Optional) In the File details section, enter a
File ID and Name for the custom string
file.
-
Select a value from the Communication settings list, and
then configure a Read key and a Write
key, or a Read-write key.
-
From the Type list, select Custom
string.
-
In the File details section, select Custom
string from the Type list.
-
Add at least one custom string to the custom string file to define what cardholder
information to encode:
-
In the Custom string section, select
UTF-16 or ASCII from the
Encoding list, and then click Add an
item ().
-
In the Custom string management dialog box, configure the
following:
- Content
- Click Add an item () and select the cardholder
information that you want to store on the card.
- Remaining space
- The number of characters remaining in the file over the total number of
characters permitted.
- Length
- Enter the maximum number of characters that you want the content to take up in
the file.
- Fill with null character
- When the option is on, if the value of the content does not use the maximum
number of characters defined in the Length, the null
character is used to fill the remaining space.
When the option is off, the
Fill field is displayed, and you can enter different
characters to use instead of the null character.
- Offset
- Where the custom string starts in the file.
- Text alignment
- Whether to align the text to the left or to the right.
-
Click OK.
The custom string is added to the custom string file in the File
selection section.
-
Add more custom strings to the custom string file, as required.
-
Click Save.
-
Encode the cardholder information and MIFARE DESFire credential on the card:
NOTE: Ensure that the MIFARE DESFire configuration task is not open
on the Test USB reader page. This prevents you from using the STid
reader in the Cardholder management task.
-
Open the Cardholder management task, and select the cardholder
from which you want to retrieve the cardholder information.
-
Click .
-
In the Automatic entry dialog box, select STid USB
reader, and ensure that the Encode before
enrollment option is on.
-
From the Configurations list, select the MIFARE DESFire
configuration that was configured with the custom string file.
-
Badge the card.
Results
The cardholder information from the cardholder you selected is encoded on the card. The
card can now be used to create a cardholder with the same values on a different
system.