Dave, thanks for your reply.
The reason why we want to protect only the login page is that all the other pages
are not confidential in nature and transmission of all the resources using https
is slow. But the password entered by the user in the login page must be protected
by ssl.
We checked the
Servlet 2.2 specification, and saw that the <login-config> element
can only contain the following sub-elements (auth-method, realm-name, form-login-config).
<form-login-config> can only contain (form-login-page, form-error-page)
Our <login-config> looks like this:
<login-config>
<auth-method>FORM</auth-method>
<realm-name>TestApp</realm-name>
<form-login-config id="FormLoginConfig_1">
<form-login-page>/login.jsp</form-login-page>
<form-error-page>/error.html</form-error-page>
</form-login-config>
</login-config>
There does not seem to be any subelement in <login-config> that can specify SSL protection
for the login page only.
Correct me if I am wrong, to my understanding the <user-data-constraint> element
containing the <transport-guarantee> applies to all the web resources specified
inside the <web-resource-collection> and if I set <transport-guarantee> to
confidential, it would apply to all web resources as well as the login page.
Is there is any different way to achieve this ?
[ February 11, 2003: Message edited by: Hari RamKrish ]