WebSphere Portal, Express Beta Version 6.1
Operating systems: i5/OS, Linux,Windows

 

Secure Socket Layer

This section provides information about adding a secure socket layer to your LDAP server.

Configuring WebSphere Portal Express for SSL adds security to the client-portal exchange. It 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 Express. In addition, assuming that the WebSphere Application Server 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 Express 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 WebSphere Application Server plugin for the Web server must be configured to forward traffic on that port to WebSphere Application Server and WebSphere Portal Express. This involves configuring the virtual host information. Finally, WebSphere Portal Express must be set up to generate self-referencing URLs using SSL as the transport.Note: 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.

After completing the following procedures, all requests, starting with the login, are encrypted.

Parent topic: Security and authentication considerations
Library | Support | Terms of use |