LogoLogo
v3.4.x
v3.4.x
  • Introduction
  • Prerequisites
  • Trust1Connector JS SDK
  • Changelog
  • Core
    • Concept
    • Quick-Migration Guide
    • Integration in Web Applications
    • Core Service
    • Consent
    • Status codes / error handeling
    • Configuration
    • Authenticated client
    • Downloading latest Trust1Connector
  • Miscellaneous
    • Troubleshooting
    • Installation FAQ
  • Token
    • Token typing models
    • Generic token
    • Belgian eID
    • Aventra MyEID PKI
    • Idemia Cosmo One v8.2
    • Oberthur Cosmo One v7.3
    • Diplad (BeLawyer)
    • Chambersign
    • Certigna
    • Certinomis
    • Jcop3
    • Airbus
  • Payment
    • Payment typing models
    • EMV
    • Crelan
  • FIle
    • File exchange
  • HSM
    • Remote loading
  • PKCS11
    • PKCS11 Objects
  • Other
    • Print
Powered by GitBook
On this page
  • Downloading Trust1Connector
  • Differentiate between MacOS architectures
  • Distribution services

Was this helpful?

Export as PDF
  1. Core

Downloading latest Trust1Connector

Downloading Trust1Connector

The T1C JS SDK no longer has a method to download the T1C installer.

Instead, the T1C installer can be downloaded by navigating the client browser to the /v3/downloads/installer endpoint of the Distribution Service (e.g. https://acc-ds.t1t.io/v3/downloads/installer). The Distribution Service will analyse the User-Agent header and automatically initiate the download of an OS-appropriate installer of the latest configured version. The user agent string parsing is considered "best-effort"; as they can vary wildly depending OS and browser software.

Alternatively, you can also initiate the download of a T1C installer with the following endpoints:

  1. /v3/downloads/installers/{{OS}}: This endpoint allows you to specify the OS for which you wish to obtain an installer. The possible values are win32, win64, unix, macos macosarm.

  2. /v3/downloads/installers/{{OS}}/versions/{{version}}: This endpoint allows you to download a specific version of a T1C installer for a specific OS.

The automatic user-agent detection does not differentiate between ARM/M1 and Intel Mac devices

Differentiate between MacOS architectures

For MacOS there are currently 2 supported architectures:

  • ARM64 (M1, ...)

  • Intel x86_64

Currently, browsers etc do not display which architecture you're running. So in order to provide download links to the users you need to provide them with the option to download any of the 2 architectures. The user needs to decide which platform he is running.

From the DS you can get both links with the following URL's (Production DS is used in the example);

# Intel x86_64
https://ds.t1t.io/v3/downloads/installers/macos

# ARM64
https://ds.t1t.io/v3/downloads/installers/macosarm

After this, you can provide the user with the choice of which one they want to download. Below you can see an example of how Google does this with their Browser, Google Chrome.

Here you can clearly see they provide two versions, with a recommendation on Intel because the majority of the users still run Intel Apple devices

Distribution services

Environment

DS url

Acceptance

https://acc-ds.t1t.io

Production

https://ds.t1t.io

PreviousAuthenticated clientNextTroubleshooting

Last updated 3 years ago

Was this helpful?