How SSL works with Middle Tier Oracle HTTP Server

How SSL works with Middle Tier Oracle HTTP Server:

1. The client sends a request to the server using HTTPS connection mode.


2. The server presents its certificate to the client. This certificate contains the server's identifying information.


3. The client checks its list of Trust points and compares the information in the certificate with the server's public key. If it matches, the server is authenticated as a trusted server.


4. The client sends the server a list of the encryption levels, or ciphers, that it can use.


5. The server receives the list and selects the strongest level of encryption that they have in common.


6. The client creates a session key which is used to encrypt the data and sends this session key to the server which can decrypt the data with its private key

Enabling SSL in Oracle E-Business Suite Release 12

The most significant change for Secure Sockets Layer (SSL) support in E-Business Suite Release 12 is the use of the mod_ossl module for the Oracle HTTP Server. Like mod_ssl, the mod_ossl plug-in enables strong cryptography for Oracle HTTP Server. In contrast to the OpenSSL module, mod_ossl is based on the Oracle implementation of SSL, which supports SSL 3, and is based on Certicom and RSA Security technology.

In Release 12 SSL certificates will be managed by the Oracle Wallet Manager 10g, which will be accessible via the familiar OWM graphical user interface (GUI) or the new ORAPKI command line interface (CLI). Since Release 12 will be using the Forms Listener Servlet a separate certificate is no longer needed for Forms. Forms will share the same wallet as the Oracle HTTP Server.