Reach an HTTPS archive with a hospital CA or a client certificate
Connect to an Orthanc or DICOMweb archive that uses a private CA or requires a client certificate.
Desktop app only, 1.6.0 or newerdcmage pro
Problem
Many hospital archives use a certificate from the hospital’s own certificate authority, and some sit behind a proxy that also asks the workstation to prove who it is with a client certificate.
Steps
-
Enter the archive’s https address. The certificate fields appear once the address starts with
https://. They are not offered on anhttpaddress, where no certificate is checked. A hospital CA that IT already installed on this computer works with no extra step. -
Add the CA certificate if this computer does not trust it yet. Choose the PEM file of the certificate authority that issued the archive’s certificate. It is trusted for this connection only and is remembered with the archive.
-
Add a client certificate if the archive asks for one. Choose the certificate and its private key, both as PEM files. The key goes to the connection and is not saved anywhere, so you choose it again each time you connect. The app remembers only that this archive needed a certificate.
-
Connect. If the archive’s certificate cannot be verified, or the archive wanted a client certificate you did not give it, the connection is refused and the message says why.
Limits
- TLS 1.2 and 1.3 only.
- The operating system applies its own rules to server certificates. macOS requires a subject alternative name that matches the address, the server-authentication usage, and a validity of no more than 825 days. A certificate that breaks one of these is refused even when its CA is trusted. Windows also refuses a certificate that does not name the address or is not usable for a server, but under a private CA it accepts a common name that names the address, even beside a subject alternative name for another one, and it sets no 825-day limit. Issue certificates to the stricter macOS rules if both kinds of computer connect.
- There is no switch to skip verification.
Result
Searches, retrievals and commits travel over the verified connection, and the remembered archive keeps the CA for next time.