Securing only the login page with WebSphere and Secure Sockets Layer
From the developerWorks archives
Date archived: January 3, 2017 | First published: May 01, 2004
Web applications that do not transmit sensitive information run faster if the transport layer does not enforce encryption. This article shows you how to configure a Web application so that Secure Sockets Layer (SSL) is used only for transmission of user IDs and passwords, and not for other information exchanged between client and server. In this way, you can improve performance and still protect user IDs and passwords, thus preventing unauthorized access to data. The article uses WebSphere Studio V5 to develop and test the application, and WebSphere Application Server to deploy it.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.