You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.