Truststore API
This module is available starting from v3.8.5
Sample code uses ES6 language features such as arrow functions and promises. For compatibility with IE11, code written with these features must be either transpiled using tools like Babel or refactored accordingly using callbacks.
Introduction
The Truststore API has been introduced to allow using any PKCS11 compatible smart card, which is available in the OS certificate or keystore. The Trust1Connector will interface to the Windows Certificate manager or the Mac Keystore using native OS mappings.
Certificates available in the certificate manager or keystore will be availabe through the generic Trust1Connector interface.
Interface
Models
Get Truststore container object
Initialise a Trust1Connector client:
Get the container service:
Call a function for the container:
Certificates
Exposes all the certificates publicly available on the store.
this has the capabilities to return multiple certificates if the store has multiple of any type.
Fetching Certificate information
Below you can find all the functions to retrieve a specific type of certificates
Response:
You can also fetch all the certificates, separated by type, at once
Sign Data
On MacOS it is not possible to provide a pin yet, this will be resolved in a future version; this feature depends on the availability of this funcitonality on the MacOS.
To get the certificates necessary for signature validation in your back-end:
Sign Hash
When the web or native application is responsible for showing the password input, the following request is used to sign a given hash:
Response is a base64 encoded signed hash:
Authenticate Data
On MacOS it is not possible to provide a pin yet, this will be resolved in a future version; this feature depends on the availability of this funcitonality on the MacOS.
To get the certificates necessary for signature validation in your back-end:
Authenticate Hash
When the web or native application is responsible for showing the password input, the following request is used to sign a given hash:
Response is a base64 encoded signed hash:
Bulk Signing
When using bulk signing, great care must be taken to validate that the first signature request was successful prior to sending subsequent requests. Failing to do this will likely result in the card being blocked.
Bulk PIN Reset
The PIN set for bulk signing can be reset by calling this method.
Response will look like:
Verify PIN
On MacOS it is not possible to provide a pin yet, this will be resolved in a future version; this feature depends on the availability of this funcitonality on the MacOS.
Verify PIN without pin-pad
When the web or native application is responsible for showing the password input, the following request is used to verify a card holder PIN:
Response:
Last updated
Was this helpful?