> For the complete documentation index, see [llms.txt](https://t1t.gitbook.io/t1c-js-guide-v3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://t1t.gitbook.io/t1c-js-guide-v3/v3.1.4/changelog.md). # Release Notes ## v3.1.4 ### Bug * File digests config doesn't take the path differences between Mac OS and Windows into account * PKCS11 configuration cookie cannot be created on Windows devices * PKCS11 returns null pointer exception when no pin is provided * Unresolved address exception when the Trust1Connector is installed or started without internet connection ### Story * As an end user I can use RMC with the new T1C v3 for the belgian eID and the file exchange * Windows installers are signed with the Trust1Team certificate * Windows installer includes the firewall settings upfront * All endpoints communicating with smartcards/tokens/... need to be protected by means of JWT * Support for silent install on Win Platforms * Remove sensitive system info from API & Proxy exposed on /info endpoint * Remove from API & Proxy the temp folder path on the /info * Provide the possibility to use PKCS11 objects instead of keystores * Integrate PKCS11 container in the sandbox-service * Maintain a transaction log with labels * Ability to do bulk signing with the generic token interface ## v3.1.3 ### Bug * PKCS11 SlotId in config issue * Fileexchange when canceling file or directory dialogs, no error is thrown but an empty path is returned * Catch errors with regards to the GRPC service nog being running * File IO needs to check if access rights for file are fulfilled otherwise return 803 * Fileexchange v2 recovery failed due to wrong encoding * T1C JS SDK fix typo for responseObject info endpoint * Typescript typings are conflicting with eachother (generics) * T1C SDK pkcs11generic slots should be numbers instead of strings ### Story * Cookie implementation for the Trust1Connector JS SDK in shared environments ## v3.1.2 ### Bug * check fileexchange file/directory access rights before executing the command * After reinstallation the v3.0.1 of the t1c api config defines its running in a shared environment but there are no other instances running on the machine * When no connector is installed no valid error code is returned in JS * Play.pid blocking reinstallation of Trust1Connector API ### Task * Move file location of the T1C v3 file-exchange config to the new folder structure instead of using the old folder structure ### Story * Audit logging for tampering checks in the Trust1Connector * Configure logging for T1C-API * Keep audit record for lifecycle changes T1C-API (restart sandbox, ...) * As an integrator I want to have the RemoteLoading functionality in REST available * Keep DS logs for 1 year * As the Trust1Connector I want the Sandbox to have an automatic recovery when an unexpected shutdown happens * Add parameter validation to each endpoint which requires it --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://t1t.gitbook.io/t1c-js-guide-v3/v3.1.4/changelog.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.