OnDemand User Group

Support Forums => Content Navigator => Topic started by: Ed_Arnold on July 22, 2020, 06:47:09 AM

Title: Chrome 84 tightening of TLS restriction
Post by: Ed_Arnold on July 22, 2020, 06:47:09 AM

Received this from one of the ICN support people:

Chrome 84 released this month implemented a TLS 1.0 / 1.1 restriction that causes a block access to ICN deployments that use the legacy protocols

Instructions to switch to TLS 1.2 on a WAS deployment:

https://www.ibm.com/support/pages/how-can-i-configure-websphere-application-server-ssl-protocol-use-tlsv12-only (https://www.ibm.com/support/pages/how-can-i-configure-websphere-application-server-ssl-protocol-use-tlsv12-only)

Video on how to manage it if standalone:

https://www.youtube.com/watch?v=SdsB71u7Ckw  (http://https://www.youtube.com/watch?v=SdsB71u7Ckw)

Title: Re: Chrome 84 tightening of TLS restriction
Post by: Ed_Arnold on July 22, 2020, 06:51:48 AM

Is ACCE is affected also?

Yes

Deprecations and removals in Chrome 84  |  Web  |  Google Developers

A round up of the deprecations and removals in Chrome 84 to help you plan.

https://developers.google.com/web/updates/2020/05/chrome-84-deps-rems (https://developers.google.com/web/updates/2020/05/chrome-84-deps-rems)

ICN 3.0 and above supports TLS 1.2

NMO 3.0.3 iF1 and above support TLS 1.2

ICN support has not found any other ICN utilities that may be affected by clients moving to TLS 1.2 (like Edit, Sync, etc.)