SSL Enforcement

To ensure your data remains secure, we are deprecating HTTP in favor of HTTPS. Adobe Livefyre will disable all HTTP and insecure SSL/TLS ciphers completely by end of August 2018. This is an Adobe Standard designed to protect the privacy of you and your users.

Who is affected?

This could impact Livefyre customers who have:

  • Server-to-server calls from their CRM, CMS, WordPress, or other Client.
  • Mobile Integrations (Android and iOS Apps)
  • Custom applications or custom code

What do I need to do?

  1. All Livefyre customers must communicate with all APIs via HTTPS for all traffic, including:

    • Server to Server Integrations (CRM, CMS, WordPress, etc.)
    • Mobile Integrations (Android and iOS Apps)
    • Custom Applications (Streamhub SDK or directly coded).
  2. Server to Server and Mobile HTTP Clients must support TLS 1.2

  3. Change hostnames from {*}.<network>.fyre.co to <network>.{*}.fyre.co. For example, the host name example.network.fyre.co changes to network.example.fyre.co``. For example:

    • bootstrap.<network_name>.fyre.co to <network_name>.bootstrap.fyre.co

    • quill.<network_name>.fyre.co to <network_name>.quill.fyre.co

    • admin.<network_name>.fyre.co to <network_name>.admin.fyre.co

How do I know whether I made the changes?

You may already use HTTPS, but Livefyre recommends you double check, especially if you have:

  • Server-to-server calls from your CMS or CRM.
  • Custom code or use SDKs for custom apps in Javascript or Mobile.
  • If your integration is more than one year old.
  • If the technology in your stack is older than one year.

Even if you already use HTTPS, you must verify that your API clients support TLS 1.2.

How can I verify that my API clients support TLS 1.2?

A person who works on the development of your site can:

  • Identify the client software.
  • Identify the version.
  • Read documentation to ensure the API client supports TLS 1.2.
  • Turn on debug mode, if needed.

Java Support for TLS 1.2

Oracle and OpenJDK JVMs for Java 8 and later are configured to use TLS 1.2, by default, for all SSL connections. You do not need to take any additional action if you use Java 8 or later.

Users of Java 7 or earlier should consult public documentation on how to enable TLS 1.2.

Why do I need to change my host names?

Livefyre does not have SSL certificates on {*}.<network>.fyre.co domains. Simply changing the URL to HTTPS breaks the application.

Do I have to upgrade to the latest version of Livefyre SDKs?

No. You can patch the code instead. To patch the code, you modify some static strings and rebuild the code. If your HTTP client is out of date, you’ll need to upgrade that as well or use a different one.

How long will this take?

The length of time this takes depends on your setup. If you have a simple implementation, it should take little time to confirm. If you have many customizations, you will need to test and deploy updated code to your servers or new Apps to App Stores. For best results, we recommend you do an initial audit of the work so you can plan for any longer-term work.

What is the timeline for completing this work?

Livefyre will disable port 80 (HTTP) to our services by the end of August 2018 and support only connections to 443 (HTTPS). Browsers and other clients, that attempt to use HTTP, will fail.

When do I need to finish this work?

All customers must use HTTPS by the end of July 2018. If you cannot meet this deadline, contact our team at prioritysupport@livefyre.com.

On this page