This article contains details specific to the use of JCOP 4.5 cards with the Idopte Middleware.

Keyset and Chip auth configuration

Configure keysets and chip auth

Some operations require one or more keysets to be defined to enable external authentication. Each keyset configuration consists of a key label in an HSM (for example connected to the Inside Server), and in most cases a key path indicating a matching key on the card.

In addition, a chip auth key config needs to be defined for all use-cases that require a secure channel. It consists of a key path and a key ID.

The following values are used in the example below:

Chip auth key config:

Do the following:

Define the keyset configuration. 

Example: Keyset configuration

You can also use mapped fields:

Example: Keyset configuration - mapped field

Configuration overview

Overwiew of which keyset and chip auth parameters to configure, depending on the use-case:

Card initialization/activation

Initialize card

• Define the initialization of the card in the encoding description (executed by the user).

Example

Example: Card initialization (PIN pad reader only)

Change and unblock PIN

Change signature/global PIN

You can change the global and/or signature PIN with the user entering the old and new PIN(s) in a dialog or through a PIN pad reader.

• Change the signature/global PIN in the encoding description. 

Example

Example: Global PIN change (via PIN pad reader or dialog, auto-detected)

Unblock signature/global PIN via SkUnblkPin

You can unblock the global and/or signature PIN, with the user entering the new PIN(s) in a dialog or on a pinpad.

• Unblock the global/signature PIN via PUK in the encoding description. 

Example

Example: Signature PIN unblocking (via PIN pad reader or dialog, auto-detected)

Unblock signature/global PIN via PUK

You can also unblock the global and/or signature PIN with the user entering the PUK and the new PIN(s) in a dialog or on a pinpad.

• Unblock the global/signature PIN via PUK in the encoding description. 

Example

Example: Signature PIN unblocking (via PIN pad reader or dialogs, auto-detected)

Delete certificates and keys

Delete certificates and RSA keys from card

You can bulk-delete all existing certificates and RSA keys from the card. Selective deletion of individual certificates and keys is not supported.

• Delete all existing certificates and RSA keys from the card in the encoding description. 

Example

Example: Delete all keys and certificates (from card)

Certificate requests

Request certificates

The current card profile supports two "containers" in which to store certificates: sign (guarded by the signature PIN) and mpp (guarded by the global PIN).

It is mandatory that you specify the location for each certificate you want to write. Valid location values are (case insensitive) Signature and MPP. Key archival or recovery is only possible with the MPP location.

For key archival you have to configure the key size either in the CA itself or via the KeySize parameter of the IDM certificate template, depending on the CA and its configuration.
For example, in Smart ID Certificate Manager you need to use a key procedure format with kar.key.type = RSA and keylength.value = 3072 in your archival procedure.

For key recovery you cannot specify the key size, as it is already pre-defined by the key to be recovered.

For PKCS#10 requests you have to set the correct key size via the KeySize parameter in the encoding description, as shown in the encoding example further below.

Three new certificates are requested in the example below: authentication, signature, and confidentiality (using key archival for the latter).

 The service task "Cert: Load Key History List" must be configured to recover just one single cert, otherwise the limit of allowed certificates can be exceeded. For more information, see section "Cert: Load Key History List" in Standard service tasks in Identity Manager.

• Define the request for multiple certificates in the encoding description.

Example

Example: Request multiple certificates

EF data containers

Read EF data objects

Smart ID Identity Manager supports reading the http://EF.Id (Card Holder Identification) and EF.Fonction (Professional information) data containers.

Do the following in the encoding description:

1. In the [Description] section, set readDataObjects to "true".

2. In the [Description] section, provide the file management keyset.

3. In the [Fields] section, add the keys of the data you want to read.

   • The keys for the EF.Fonction container are ef.function.job, ef.function.postingPlace and ef.function.productionDate.

   • The keys for the http://EF.Id container are ef.id.familyName, ef.id.firstName, ef.id.rio, ef.id.uin, ef.id.orgName1 and ef.id.orgName2.

4. In the Encoding Fields tab, set the added fields to "Read" and map them to a process variable.

Example

Example: Reading of EF data objects

Update EF data containers

Smart ID Identity Manager supports updating the http://EF.Id (Card Holder Identification) and EF.Fonction (Professional information) data containers.

Do the following in the encoding description:

1. In the [Description] section, provide the file management keyset.

2. In the [Description] section, set the keys of the data you want to update and map them to a field. Any keys you omit will keep their old value.

   • The keys for the EF.Fonction container are ef.function.job, ef.function.postingPlace and ef.function.productionDate.

   • The keys for the http://EF.Id container are ef.id.familyName, ef.id.firstName, ef.id.rio, ef.id.uin, ef.id.orgName1, and ef.id.orgName2.

3. In the [Fields] section, define the fields you referenced in the previous step.

4. In the Encoding Fields tab, set the value of the fields. To clear a field in a data container, map it to an empty value.

Example

Example: Update EF data objects

Limitations

Card firmware requirements for pinpad readers

Creating certificates and keys on JCOP 4.5 cards requires card firmware with support for chained APDUs when used with certain pinpad readers (e.g. Xiring / Ingenico Leo series).
For those readers the cards need to have version 4.1.1 of the Chipdoc applet.

Limited support for pre-release cards

Pre-release cards produced before 2023-10-12 are not supported due to a flaw in the card profile fixed in later revisions.
It would prevent proper authentication for write access to EF data containers.

Additional information