Besides writing certificates and keys, the Pkcs#11 interfaces also allow to write arbitrary data objects on the smart card. This is now supported by Smart ID Identity Manager with different middleware. This is not supported with Nexus Personal Desktop Client.
The sort order of card applications (encodings) was not deterministic when exporting/importing the configuration. Now a sort column has been added. When saving or importing a card template, the correct sort order will be persisted and used by Card production. For more information, see Upgrade Smart ID Identity Manager from 23.04.10 to 23.04.11.
CRED-15230
The performance of the history signature chain verification has been improved by enabling the verification in multiple threads. A new parameter "commonHistoryService.SignatureVerifyThreads" has been added for this. See List of Identity Manager system properties for more information.
CRED-16290
When exporting search results, translations now also include meta-fields like status and boolean fields and use the date-format of the user's locale.
CRED-16360
When using Idopte Middleware, it is now possible to have the PIN of the card entered and checked before certificates are renewed in addition to identify with the adminkey.
CRED-16536
The D-Trust Certificate Service Manager API was based on SOAP but is now in the process of being replaced by a RESTful API. Smart ID Identity Manager now offers the option to use both, enabling customers to switch from one to the other.
When pushing a CRL from Certificate Manager to Identity Manager, a response is now sent to Certificate Manager after the full list has been received and the signature verified. It is not waiting for Identity Manager to process the entire list.
Corrected bugs
Jira ticket no
Description
CRED-13724
There was an issue with wrong dates when creating.ics files. This has been fixed.
CRED-16452
The name of the default attestation key has been changed in the respective Messaging Service tasks.
There was an issue where messages from Scheduled Jobs were logged to idm_rf.log instead of idm_synch.log with the delivered log4j configuration file. This has been fixed.
Other components in Smart ID
Digital Access
This release does not contain any specific updates for the Digital Access component.
Physical Access
This release does not contain any specific updates for the Physical Access component.
Smart ID Messaging
This release does not contain any specific updates for the Smart ID Messaging component.
For details on the updated Smart ID deployment configurations, see:
Smart ID deployment configuration release note
-
Contact and support
For information regarding support, training, and other services in your area, visit www.nexusgroup.com/. Nexus offers maintenance and support services for Smart ID components to customers and partners.
For more information, go to Nexus Technical Support or contact your local sales representative.
