Secure Socket Layer



Search Tips   |   Advanced Search


Configure WebSphere Portal for SSL adds security to the client-portal exchange. SSL encrypts all traffic between the client browser and the server, so that no one can "eavesdrop" on the information that is exchanged over the network between the client browser and WebSphere Portal.

In addition, assuming that the IBM WAS is also configured to accept (or even require) SSL connections, the LTPA Token and other security and session information can be completely protected against hijack and replay attacks. Configuring WebSphere Portal for SSL is a multistep process that involves configuring the following components:

In general, the Web server must be configured to accept inbound SSL traffic.

Then, the WAS plug-in for the Web server must be configured to forward traffic on that port to WAS and WebSphere Portal. This involves configuring the virtual host information.

Finally, WebSphere Portal must be set up to generate self-referencing URLs using SSL as the transport.

This procedure might be slightly different if a front-end security proxy server such as Tivoli Access Manager WebSEAL is used. In that case, the front-end security server handles the client SSL connections. The Web server receives connections from the front-end security proxy server. Mutually authenticated SSL could be configured in the Web server and the front-end security proxy server if needed. This is highly dependent on the security requirements of each deployment.

Parent topic:

Security and authentication