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 following page describes how you can integrate the Certigna module exposed on the Trust1Connector onto your web application.
Because we're using the generic interface we can define the module variable upfront since we know we want to use the certigna integration.
Certificates
Exposes all the certificates publicly available on the smart card.
Authentication Certificate
Contains the 'authentication certificate' stored on the smart card. The 'authentication certificate' contains the public key corresponding to the private RSA authentication key. The 'authentication certificate' is needed for pin validation and authentication. When additional parsing of the certificate is needed you can add a boolean to indicate if you want to parse the certificate or not
The service can be called:
{"certificate": {"certificate":"MIIFjjCCA3agAwIBAgIIO...xg==","parsedCertificate": {...} },// OR if multiple certificates"certificates" [ {"certificate": {"certificate":"MIIFjjCCA3agAwIBAgIIO...xg==","parsedCertificate": {...} } } ]}
Non-repudiation Certificate
Contains the 'non-repudiation certificate' stored on the smart card. The 'non-repudiation certificate' contains the public key corresponding the private RSA non-repudiation key. When additional parsing of the certificate is needed you can add a boolean to indicate if you want to parse the certificate or not
The service can be called:
The 'algorithm_reference' property can contain the following values: sha1, sha256, sha512, md5.
The core services lists connected readers, and if they have pin-pad capability. You can find more information in the Core Service documentation on how to verify card reader capabilities.
Bulk Signing
It is possible to bulk sign data without having to re-enter the PIN by adding an optional bulk parameter set to true to the request. Subsequent sign requests will not require the PIN to be re-entered until a request with bulk being set to false is sent, or the Bulk Sign Reset method is called.
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.
When the web or native application is responsible for showing the password input, the following request is used to verify a card holder PIN:
var data = {"pin":"..."}generic.verifyPin(module, data, callback);
Response:
{"verified": true}
Verify PIN with pin-pad
When the pin entry is done on the pin-pad, the following request is used to verify a given PIN:
var data = {}generic.verifyPin(module, data, callback);
Response:
{"verified": true}
Authentication
The T1C-GCL is able to authenticate a card holder based on a challenge. The challenge can be:
provided by an external service
provided by the smart card
An authentication can be interpreted as a signature use case, the challenge is signed data, that can be validated in a back-end process.
External Challenge
An external challenge is provided in the data property of the following example:
var data = {"pin":"...","algorithm_reference":"sha1","data":"I2e+u/sgy7fYgh+DWA0p2jzXQ7E="}generic.authenticate(module, data, callback);