Spok response to TLS 1.0 and 1.1 decommission

Q:  Am I impacted by the end of developer support for TLS 1.0 and 1.1?

A:  That depends on what products you are running and their version.  Please see the Spok Software Lifecycle Dates for product and version details.

If you have upgraded to Care Connect 1.9 you won’t be impacted.  However, if you are running the following product and version combinations – or earlier – you will be impacted if you use https.

• Smart Suite 5.7 or older
• eNotify 5.7 or older
• Spok Console 7.9 or older
• MediCall 11.9 or older
• Spok Mobile 4.4 or older
• Spok Messenger 5.11 or older

Q:  If I am running a version that is impacted what will my end users experience?

A:  When users browse to a secure Spok webpage, they will be presented with a warning message stating that the site they are going to is not secure.  The end user will need to click through the warnings to gain access to the desired webpage.

Note:  Work with your security team to ensure that end users can continue to click through to the TLS 1.0/1.1 secured Spok web pages and that this is not locked down by a security group policy.

Q:  How do I fix this in the long term?

A:  Contact your Spok Sales representative to start discussing a path to upgrade to the latest version of your Spok product.

Q:  Can I change the Spok TLS version to 1.2?

A:  You cannot simply apply a new version of TLS to your Spok solution.  TLS 1.2 was incorporated into the code and infrastructure requirements for Care Connect 1.9 products only. 

Q:  Can I disable TLS 1.0 and 1.1 on my servers?

A:  Older versions of Spok are dependent on the older versions of TLS.  Removing or disabling them will negatively impact your Spok solution.  The only way to remediate this issue is to upgrade to Care Connect 1.9.

If you have further questions, please open a support case with Spok Support at www.spok.com/myspok.