T1C-JS Guide
  • Introduction
  • Core
    • Introduction
    • Concepts
    • Source Code
    • Overview Client API
    • Client Configuration
    • GCL Configuration
    • Core Services
    • Consent
    • Generic Interface
    • Status codes
    • OCV Services
    • Frequently Asked Questions
    • Troubleshooting
  • Containers
    • eID
      • Belgian eID
      • Luxembourg ID
      • Portugese eID
      • Spanish DNIe
    • Payment
      • EMV
    • PKCS
      • PKCS #11
      • PKCS #15
    • PKI
      • Aventra
      • LuxTrust SmartCard/Signing Stick
      • Oberthur
      • PIV
    • Token
      • SafeNet
      • YubiKey
    • Transport
      • Mobib
    • Other
      • File Exchange
      • Ocra HOTP
      • Remote Loading
Powered by GitBook
On this page
  • Introduction
  • Characteristics of T1C-GCL

Introduction

NextIntroduction

Last updated 7 years ago

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 an unmanaged device. 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 an unmanaged 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): a secured back-end in order to distribute and manage running T1C-GCL instances

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

Additional plugins (community and private plugins) are in development. Additional client libraries for native applications are in development.

Characteristics of T1C-GCL

Because the T1C-GCL runs on unmanaged devices, the T1C-GCL has some important specifications:

  • browser independent (no impact upon browser update)

  • not in need of a browser plugin

  • based on official communication standards

  • 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

Trust1Connector