An encoding description contains the information for the electronic personalization of a card. You import the encoding description from a file.
This article describes some simple use cases as templates for basic encoding descriptions. These templates are complete in the sense that they can be used "as is", but they cover only simple use-cases. This can be used in Nexus PRIME.
Create an encoding
To create an encoding:
Copy the code block into a text file and save it with the ending .dsc
Produce a card with CardSDK using a PKCS10 request (= create key pairs on card)
The use case is to:
initialize the card,
generate two key pairs on the smartcard,
request two certificates by PKCS#10 and
write them to the card (by use of certificate templates defined in PRIME Designer: "authentication": AuthCertificate and "signature": NonRepudiationCertificate),
where initial PIN and PUK are provided by the application
Define like this in the encoding description:
[Encoding]
Type=1024,Chip
Devices=8710
[Fields]
AuthCertificate.DN=
NonRepudiationCertificate.DN=
PINField=
PUKField=
[Description]
PKCS11Library=cvP11.dll
; Card initializaion, set initial PIN & PUK provided by server application, hard coded initial label
InitToken=true
InitialPUK=PUKField
SetPin=true
PIN=PINField
InitialLabel=#neXus
ClearFields=PINField,PUKField
Applicationlist=AB
[Application_A]
CertTempl=AuthCertificate
[Application_B]
CertTempl=SigCertificate
Renew a card with CardSDK using Cryptovision middleware
The use case is to:
(re-)initialize the card,
generate two key pairs on the smartcard,
request two certificates by PKCS#10 and
write them to the card (by use of certificate templates defined in PRIME Designer: "authentication": AuthCertificate and "signature": NonRepudiationCertificate),
where initial PUK is provided by the application and PIN is entered by the user.