TLS

Legacy Contributor

Hello....When upgrading to ADFS....do we also need to upgrade to TLS V2?

Find more posts tagged with

Comments

Legacy Contributor

Upgrade to TLS 1.2 is NOT a requirement.

Legacy Contributor

Thank you for your response. Would you also know if on-premise customers need to upgrade to TLS 1.2 by April to stay in support with Infor?

Legacy Contributor

It depends. If you use Infor-hosted items (e.g. ENWISEN), it's possible you may need to implement TLS 1.2 on the items that touch it. Also if you use procurement or EDI, many EDI or Punchout vendors may start requiring you to use TLS 1.2 for relevant communication. Also if you switch to ADFS, you may be required to use TLS 1.2, depending on your ADFS setup. Some browser versions may flag lower TLS levels as a "warning" or "error". However, to my knowledge there is nothing in a current version of Infor LSF or LM products that requires you switch to TLS 1.2.

In summary, TLS 1.2 requirement may come from third-party components or hosted services, but probably not from Infor on-premise components directly.

Legacy Contributor

Thank you for your information.....I thought we had to switch to ADFS....and I do not remember seeing anywhere that we needed to upgrade to TLS 1.2

Legacy Contributor

Thank you Alex....I'm working with a Lawson consultant for ADFS and he is installing that on our Mingle server...sounds like I could request him to just not make TLS1.2 a requirement....our Websphere Protocol is SSL_TLS...hopefully we can just stay at that?

Brian Allen

Note that all of the major browsers will stop supporting TLS 1.0 and 1.1 on March 31st, 2020. I've been checking into this and found that Infor does have a stance - KB 2010080 - Requirements for Infor Lawson Products to use TLS 1.2 Protocol.

TLS is used for secure connections and the protocol used during an https connection is determined by the browser and the server. On a connection request, the browser will send the server all of the protocols it supports and the server will generally connect at the highest version it also supports. I've confirmed that all of our S3 and Landmark connections on Chrome and Internet Explorer are running TLS 1.2 and have likely been doing that for several years (as long as the browser and server have supported it). TLS 1.2 was released in 2008. You can check your browser supported TLS version here: https://tls-test.icims.com/

So although S3 10.0.9 ESP is the first certified release for TLS 1.2, the 10.0.8 release has been working well for some time for us. We already have a project in place to upgrade to the latest release levels before we were aware of the browser changes. I've copied the Infor response to consider below.

Inforxtreme response - Event Note: 10.0.8 has not been tested or verified with TLS 1.2 so we do not know what may or may not work. There is a chance that most things function as expected, but again since has not been tested we do not know for sure.

10.0.9 is the first supported release that supports TLS 1.2, we would strongly encourage that you be on this release.

Brian Allen

You can check the TLS connection version you are running for Lawson in Chrome by right clicking the page, selecting Inspect, then selecting the Security tab. That doesn't mean that Lawson will fully support that TLS version.

Copyright © 2025 Infor. All rights reserved.