How To configure DB Console and Agent to use Stronger Ciphers for the SSL Communication
(Doc ID 604903.1)
Last updated on NOVEMBER 16, 2022
Applies to:
Enterprise Manager for Oracle Database - Version 11.1.0.7 to 11.2.0.4 [Release 11.1 to 11.2]Information in this document applies to any platform.
Goal
Configuring the 11.1.0.7 and above Database (DB) Control web site and agent running in secure mode to use stronger ciphers is described below.
Note:
Also consider the following for a jdk bug related to SSL:
<Document 1946195.1> - CVE-2014-3566 Instructions to Mitigate the SSL v3.0 Vulnerability (aka "Poodle Attack") in Oracle Database Control
Also consider the following for a jdk bug related to SSL:
<Document 1946195.1> - CVE-2014-3566 Instructions to Mitigate the SSL v3.0 Vulnerability (aka "Poodle Attack") in Oracle Database Control
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| What are the default and available values |
| How to change the SSL cipher suite for the DB Console port |
| How to change the SSL cipher suite for the EM Agent port. |
| How to disable SSL |
| How to disable SSLv2: |
| References |