Introduction
Last updated
Last updated
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
Host the Trust1Connector v3 OpenAPI Definition on the Distribution Service
Integrate Certigna into RMC application
Integrate Certinomis into RMC application
Upgrade to latest T1C Javascript
Add MacOS ARM OS enumeration to the possible PackageOS's
[DIS-33] - Allow wildcards in CORS whitelist
[DIS-34] - Add remote loading to RMC
[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
[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
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.
[DIS-19] - Application tokens use label name as subject instead of label id
[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
[DIS-16] - Bootstrapping the gateway in v3.0.2 fails
[DIS-17] - Bootstrapping the gateway restores all data on the gateway
[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
[DIS-2] - Add flags for display modal and implicit creation in file-exchange
[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
[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
