Following instruction on this page you can test if your client has support for a necessary cipher suite required by our servers.
On the host that runs your service run the next command:
curl -o /dev/null -s -vvv https://my.patientsknowbest.com
Expected success output
* Trying 35.246.122.93:443... ... * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 ... * Connection #0 to host my.patientsknowbest.com left intact
SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 indicates that the host OS supports TLS_AES_256_GCM_SHA384TLSv1.3 which is one cipher suite that our servers also support.
TIP: Version of your integration engine running on the given host might not support any of the cipher suites that our servers support.
NEXT: Consult documentation of your integration enginge to see what cupher suites it supports.
TIP: client software might be outdated or missing security updates (can be OS and/or integration engine version).
NEXT: See way to update your client software.
Expected failure output
* Trying 35.246.122.93:443...
* Connected to my.patientsknowbest.com (35.246.122.93) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ECDHE-RSA-AES256-SHA384
* CAfile: /etc/ssl/certs/ca-certificates.crt
* CApath: /etc/ssl/certs
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
} [5 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [181 bytes data]
* TLSv1.2 (IN), TLS header, Unknown (21):
{ [5 bytes data]
* TLSv1.2 (IN), TLS alert, handshake failure (552):
{ [2 bytes data]
* error:0A000410:SSL routines::sslv3 alert handshake failure
* Closing connection 0
* error:0A000410:SSL routines::sslv3 alert handshake failure indicates lack of ovelap in cipher suites supported by client and server.
NEXT: Consult documentation of your integration enginge to see what cupher suites it supports.
TIP: client software might be outdated or missing security updates (can be OS and/or integration engine version).
NEXT: See way to update your client software.