An encoding description contains the information for the electronic personalization of a card. To create an encoding description, you must import the encoding definition from a file. This can be used in Smart ID Identity Manager.
This article describes how to block the PIN of a card right after personalization for security reasons, that is, the card can not be used further. Later - as soon as the user picks up the card from card administration office - the user has to unblock the card to be able use it.
See also Structure of an encoding description.
| Expand |
|---|
|
This use case describes how to block the PIN of a card right after personalization, for security reasons, that is, the card can not be used further. The user has to unblock the card in order to be able use it. Define like this in the encoding description:
| Code Block |
|---|
[Application_B]
BlockCard=true |
Description of the elements
| Element | Description |
|---|
BlockCard=true | Triggers the card/PIN blocking mechanism |
|
| Expand |
|---|
| title | Unblock the PIN of a card (online) |
|---|
|
Online Unblocking with PUKFor unblocking via standard P11 you can use the InitialPUK to set a new PIN (and optionally a new PUK, unless that is prevented by the card profile). Define like this in the encoding description:
| Code Block |
|---|
[Description]
SetPIN=true
PIN=#123456
InitialPUK=#12345678
PUK=#13579 |
Description of the elements
| Element | Description |
|---|
SetPIN=true | Triggers to set PIN and/or PUK, that is, the Unblocking use case. | | PIN=... | Defines the new PIN. (Theoretically also optional if you just want to set a new PUK, however, in the Unblocking use case, it is reasonable to set the new PIN here, for example, by "PIN=!FROM_USER_DIALOG_2_FIELD") | | InitialPUK=... | Defines the old PUK.
Mandatory, except for Gemalto cards and pre-initialized CardOS cards that use a CardManagerKey instead | | PUK=... | If you want to define a new PUK. (Optional, changing the PUK might not always be supported depending on the card profile) |
Online Unblocking with CardManagerKeyThe following applies to Gemalto middlewares and card, as well as to specially pre-initialized CardOS cards used with the CardOS 5.3 middleware (5.4W14 or later recommended). It does not apply to offline-unblockable cards created with the Cryptovision middleware, which uses a different approach (see below). Instead of InitialPUK / PUK,, the CardManagerKey attribute plus its NewCardManagerKey counterpart are used in the encoding descriptions. The following example uses the current key to set the PIN as well as setting a new key: Define like this in the encoding description:
| Code Block |
|---|
[Fields]
ADMIN_KEY=
NEW_ADMIN_KEY=
PIN=
[Description]
SetPIN=true
PIN=PIN
CardManagerKey=ADMIN_KEY
NewCardManagerKey=NEW_ADMIN_KEY |
Description of the elements
| Element | Description |
|---|
SetPIN=true | Triggers to set PIN and/or CardManagerKey, that is, the Unblocking use case. | | PIN=... | Defines the new PIN. (Theoretically also optional if you just want to set a new PUK, however, in the Unblocking use case, it is reasonable to set the new PIN here, for example, by "PIN=!FROM_USER_DIALOG_2_FIELD") | | CardManagerKey=... | Defines the old CardManagerKey. | | NewCardManagerKey=... | If you want to define a new CardManagerKey. |
Before you use any P11 operations on a card, make sure you first set the PIN via the CardManagerKey (like in the example code above) - once that is done, all P11 operations that require a PIN will work as usual (as long as no PUK/InitialPUK is involved as well!) and do not require the CardManagerKey.
|
...
