Chapter 14: Tomcat Security The HTTPS client certificate
Chapter 14: Tomcat Security The HTTPS client certificate mechanism is, of course, quite secure. If the public key architecture upon which HTTPS client authentication is based were defeated, the very basis of secure e-commerce would fall with it. Beyond this apocalyptic scenario, however, are some potential weaknesses: . Key length: The most important factor in the security of public key encryption is the length of the key used to encrypt the messages. As computing evolves and computing power increases, ever larger keys will be needed to maintain security against brute force hack attempts. Administrators should stay informed about public key architecture issues and upgrade the keys used should this become necessary in the future. . Theft: The fundamental assumption of public key authentication is that the corresponding private key is available only to the trusted party. Should the private key be stolen, the authentication would be compromised. While quite secure, the HTTPS client certificate mechanism is rarely used outside of business-to-business applications because of the complexity of the process one must go through (and associated cost) to obtain a certificate for each authenticating client. Configuring Authentication In order for a Web application to use one of the authentication mechanisms just described, it must be configured to do so inside its deployment descriptor ( web.xmlfile). This is accomplished by adding
For reliable and cheap web hosting services please check cheap web hosting website.