Introduction

The Trust1Connector Distribution Service is a secured central platform for the Trust1Connector that:

  • Distributes and manages running individual Trust1Connector instances

  • Manages the creation of and access for consuming applications

Changelog

v3.5.1

Story

  • Update the gateway bootstrapping script to include new CORS configuration context path

  • When creating an implicit version, generate the installer URIs from a configurable template convention

  • Create versions implicitly when a new device version registers

  • Make the DS server CORS list dynamic

  • Keep a single CORS list instead of versioned

  • Add a CORS filter to the DS

v3.5.0

Story

  • Remove the RMC demo application from the DS so that it can be a separate application

  • Update gateway bootstrapping for new versioned context path

  • Implement consent flow for centralized device agent registry

  • Change the DS context path to v3_5 in order to allow concurrent deployment with previous version

  • Implement device agent registration in DS

  • Replaced JWE device auth by JWS device auth for Rust implementation of T1C

v3.0.13

Bug

  • Previous version was not built with Java LTS version

v3.0.12

Story

  • Update RMC JS SDK

v3.0.11

Story

  • Host the Trust1Connector v3 OpenAPI Definition on the Distribution Service

v3.0.10

Story

  • Integrate Certigna into RMC application

  • Integrate Certinomis into RMC application

v3.0.9

Story

  • Upgrade to latest T1C Javascript

v3.0.8

Story

  • Add MacOS ARM OS enumeration to the possible PackageOS's

v3.0.7

Story

  • [DIS-33] - Allow wildcards in CORS whitelist

v3.0.6

Story

  • [DIS-34] - Add remote loading to RMC

v3.0.5

Bug

  • [DIS-21] - SSL keystore download does not work if SSL config was not created last

  • [DIS-28] - The DS certificate keystore cannot be found if path contains spaces

  • [DIS-30] - Labels are not validated when syncing transactions

Story

  • [DIS-22] - Add e-herkenning to RMC

  • [DIS-26] - Provide T1C-DS communication endpoints with JWE in body instead of headers

  • [DIS-27] - Allow the DS to be run as a standalone server package

  • [DIS-29] - Update error codes in RMC

  • [DIS-31] - Add the print module to the RMC application

v3.0.4

Added configuration environment variables for RMC:

  • T1C_DOMAIN: The domain the T1C runs on, e.g. t1c.t1t.io.

  • T1C_PORT: The port the T1C runs on, e.g. 51983.

Bug

  • [DIS-19] - Application tokens use label name as subject instead of label id

Story

  • [DIS-14] - Integrate JWT authentication for the Trust1Connector into the RMC application

  • [DIS-18] - Dynamically manage available device modules in the distribution service

  • [DIS-20] - Retrieve T1C port and domain config from DS

v3.0.3

Bug

  • [DIS-16] - Bootstrapping the gateway in v3.0.2 fails

Story

  • [DIS-17] - Bootstrapping the gateway restores all data on the gateway

v3.0.2

Bug

  • [DIS-3] - File digests config doesn't take the path differences between Mac OS and Windows into account

  • [DIS-4] - Get file information default value needs to be undefined

Task

  • [DIS-2] - Add flags for display modal and implicit creation in file-exchange

Story

  • [DIS-11] - Store device counters and aggregate data over time

  • [DIS-13] - Parse User Agent Headers

  • [DIS-15] - Integrate the implicit consent flow into the RMC application

v3.0.0

Story

  • [DIS-5] - Implement GUI for BEID

  • [DIS-6] - Implement GUI for EMV

  • [DIS-7] - Implement GUI for PKCS11

  • [DIS-8] - Implement GUI for File-exchange

  • [DIS-9] - Implement GUI for info page