At confluence it can change the cipher suite from the current one to the "SSL inspection (legacy)" c

Moises Gamez July 22, 2022

since an analysis of the cipher suite used for the connection is done, it is TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384. Unfortunately, the cipher suite does not support legacy SSL inspection, even if you register the certificate.

Link enabled for TLS traffic inspection, encryption supports advanced TLS traffic inspection. However, the feature only supports traffic from Nginx, Apache, and HAProxy.
You can change that encrypted parameter from the current one to the "SSL inspection (legacy)" column.

If the change is made, can it generate any inconvenience?

 

 

1 answer

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 23, 2022

You won't have any problems with the application if you make this change.

Except for people using legacy browsers that can't handle it.  But they should have updated years ago, any problems are theirs, not yours.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events