This is an update to a blog article posted here regarding browsers (including Firefox, Chrome, Internet Explorer and Safari) that may no longer support either TLS 1.0 or 1.1.  In addition to browser desupport of TLS 1.0 and 1.1, Microsoft has announced desupport of TLS 1.0 and TLS 1.1 with other products including Office 365.  You may go here to review more information regarding TLS 1.2 and Office 365.

Most likely, many of you have already migrated from SSL to TLS for Oracle E-Business Suite (EBS) 12.2 and 12.1: however, you should also make certain that you have patched and configured EBS properly for TLS 1.2.  You have the option to configure EBS with TLS 1.0 and 1.1; however, we highly recommend that you configure EBS with TLS 1.2 only.

If your EBS environment is not patched and configured properly, then once the third-party product desupports TLS 1.0 and/or TLS 1.1, then you may encounter issues with EBS.  Examples of the issues you may encounter include the inability to access EBS from certain browsers, the inability to access allowed redirects and errors with workflow. 

What Do You Need to Do?

1. Understand desupport notices for TLS 1.0 and TLS 1.1 for third-party products used by your organization.

  • Reach out to your third-party product vendors for more information regarding their desupport policies.

2. Follow our documentation to meet the requirements for using TLS 1.2 with Oracle E-Business Suite Release 12.2 or 12.1:

Note:  There are a number of requirements for using TLS with EBS including upgrading to JDK 7.  The end of error correction support (Extended Support) for JDK 6 was December 2018. We highly recommend that all customer upgrade to JDK 7 as soon as possible.

3. Apply the required technology and application patches to add TLS 1.2 support for the Java Workflow Mailer in EBS with and Office 365 as per the following: 

Related Articles

References