Trust1Connectorcore services address communication functionality with local, unmanaged devices. The
Trust1Connectorcore exposes 2 main interfaces:
Trust1Connector'score interface for web/native applications. The GCL exposes protected and unprotected resources.
Trust1ConnectorCore with default plugins)
Trust1ConnectorInitialization (administration resource)
Trust1ConnectorInformation (administration resource)
communicationwith device hardware. The document highlights communication with smart card readers - contact and contact-less. In the future, documentation will be updates with information for USB and Bluetooth connectivity.
card-element when a card is inserted into the card reader.
List card-readers, when a smart-card is inserted/detected, the reader will contain the cart-type based on the ATR. The ATR (Anwser To Reset), is the response from any smart-card when powered, and defines the card type. The
Trust1Connectorrecognized more than 3k smart-card types.
List card-readers, when a card-reader has pin-pad capabilities, this will be mentioned in the response (notice the
List card-readerson a device with 4 different card-readers attached:
idwhich can be used for other functions where a card-reader id is needed. This method can be requested in order to list all available card-readers, and optional cards-inserted. Each card-reader has a vendor provided name, which is retrieved from the card-reader itself. An additional property
booleanvalue, denotes if the card-reader has pin-pad capabilities. A pin-pad is a card-reader, most of the times with its own display and key-pad. From a security perspective, it's considered best practice to use as much as possible pin-pad capabilities of a pin-pad card-reader. When a reader has a smart-card inserted (contact interface) or detected (contactless interface), the card type will be resolved by the GCL in order to respond with a meaningfull type. In the above examples you see that; one card-reader has a Belgian eID card; another card-reader has a
VISA Cardavailable for interaction.
idreceived from the previous call
cardproperty when a smart-card is inserted or detected:
reader_idand contains information about a connected smart card. A smart card is of a certain type. The
Trust1Connectordetects the type of the smart card and returns this information in the JSON response.
Register Device. Upon initialization the T1C-JS will try to retrieve a valid JWT in order to check for updates.
client credentialaccess token. The access token will be used to retrieve a JWT for administration purposes, only when needed and in a
verify GCL URI
get info OS
return OS info
download installer and execute
secondsToPollReaderexpects an integer and denotes the total time span to detect card-readers.
secondsare elapsed without finding a reader
secondsToPollCardobject provides a
timeoutvalue (in milliseconds) for detecting a card; this is the time the application is willing to wait for a card-reader to be connected and a card to be detected. Default callback definition:
secondsare elapsed without detecting a card
download-modalprovides user information about the actions that should be done upon first use. The user will be presented a link, which downloads an installer. After a successful download the user can launch the installer in order to setup a GCL service. The correct GCL installer is provided depending on the browser information captured from the T1C-JS library.
list card-readersfunction, when the result is an empty JSON, one could show a modal to connect a card-reader. One or more card readers can be connected, and the T1C-JS can operate easily with all connected card-readers at the same time. In order to demonstrate the
Connect Reader Modal, we'll start requesting for card-readers:
dsproperty in this response, it means that no T1C-DS public key was set yet.