Q&A

Q1:	Why doesn't the servlet engine prompt me for authentication information?
A1:	Most likely it's because the servlet engine doesn't support the kind of authentication you want. If the servlet engine doesn't support authentication, you might still be able to use the Web server's authentication if the servlet engine is just acting as a plug-in for a Web server such as Apache or Netscape. Another possibility is that even though you changed the servlet configuration to require authentication, you might have forgotten to restart the servlet engine to pick up the changes.
Q2:	Why doesn't the servlet engine pass me the certificate information when I use SSL?
A2:	Although most servlet engines support client certificates, there are still cases when you don't receive the certificate information. Occasionally, the problem is simply that the servlet engine doesn't support client certificates. The more common problem occurs when the servlet engine acts as a plug-in to a Web server. You are less likely to get the certificate information because the Web server probably isn't passing the information to the servlet engine in the first place.