T1C-JS Guide (v2)
T1C-JS Guide (v2)
Introduction
Core
Introduction
Concepts
What's new in v2
Migration Guide [v1 -> v2]
Source Code
Backward Compatibility
Overview Client API
Client Configuration
GCL Configuration
Core Services
Citrix
Consent
Generic Interface
Status codes
Upgrade Guide
Operations guide
Operational steps
Frequently Asked Questions
Containers
eID
Payment
PKCS
PKI
Token
Transport
Other
Powered by GitBook

Introduction

Trust1Connector

Introduction

This is a guide to use the T1C-Js client for the T1C-GCL (Generic Connector Library). Trust1Connector is a product of Trust1Team in order to facilitate browser independent hardware communication from a web application with a device. The Trust1Connector guarantees a secured communication channel from a remote device, through your application until your backend services. The web application serves as a mediator in order to implement business flows. A web application stays in control for service requests towards a central back-end, and service requests with a remote device. The Trust1Connector consists of:

  • T1C-GCL (Generic Connector Library): an one-time installer for OSX, Windows, Linux

  • T1C-DS (Distribution Service for T1C-GCL): an optional secured back-end in order to distribute and manage running T1C-GCL instances

  • T1C-JS (JavaScript SDK): an optional JavaScript client library in order to facilitate the communication towards T1C-GCL and T1C-DS

  • T1C-lib-Java (Java SDK): an optional Java client library in order to facilitate the communication towards the T1C-GCL and T1C-DS

Both community and private containers can be deployed remotely without the need to re-install on the customer side.

Characteristics of T1C-GCL

Because the Trust1Connector is a secured communication layer between your application and remote hardware, the Trust1Connector has some important properties:

  • browser independent (no impact upon browser update, works on all browsers)

  • not in need of a browser plugin, applet or runtime environment

  • based on official communication standards and specifications

  • no additional software needed (for example no need of a Java virtual machine)

  • small footprint (+-2MB)

  • coops with multiple card readers (contact and contactless)

  • coops with multiple connected cards of different types

  • extendable community framework

  • installer compiled for OSX, Windows, Linux on new operation systems can be added to the supported OS list

  • same solution for shared environments

  • optional distributed release management

  • intelligent component operating only in your own application context

  • application stays in controle of the complete flow

  • idempotent local services container registry

Next - Core
Introduction
Last updated 1 year ago
Contents
Introduction
Characteristics of T1C-GCL