How to Enable/Disable JSSE in Weblogic Server in 11g/12c

JSSE Advantages

SHA-2 signed certificates are supported in the JSSE SSL implementation provided in WebLogic Server.

The JSSE-based implementation supports TLS V1.0, TLS V1.1, and TLS V1.2. Also to enable support for the TLS V1.1 and TLS V1.2 protocols, WebLogic Server must be running with JDK 7. Note Latest Version JDK 1.6 also supports these TLS version

How to enable JSSE in Weblogic Server

(1) Login to Weblogic Console

(2) Click on Lock and Edit

(3) Navigate to Environment > Servers and select the server where you want to change it

(4) Now go to the SSL tab and then go to the advanced section and click on JSSE enabled

(5) Save the changes and release the configuration

(6) You can restart the Managed server and it will start using JSSE

An alternative way to enable JSSE

You can also enable JSSE by settings these parameters in JAVA_OPTIONS.

-Dweblogic.ssl.JSSEEnabled=true

-Dweblogic.security.SSL.enableJSSE=true

This can be set in $DOMAIN_HOME/bin/setDomainEnv.sh or wherever JAVA_OPTION are being picked up

JSSE in Oracle WebLogic Server 12c

Certicom is disabled in Oracle Weblogic server 12c and JSSE is enabled by default. We cannot disable the JSSE in Oracle Weblogic Server 12c

Even if you set these options to false,

-Dweblogic.ssl.JSSEEnabled=false

-Dweblogic.security.SSL.enableJSSE=false

Oracle Weblogic server will ignore these parameters

If you like please follow and comment

Comments

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...

foalabs

Search This Blog