DO NOT REPLY [Bug 5976] - Tomcat 4.0.2B2 + Security Manager + JSSE don't work together

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5976>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5976

Tomcat 4.0.2B2 + Security Manager + JSSE don't work together





------- Additional Comments From glenn@apache.org  2002-02-28 03:21 -------
I have had no problem using Tomcat 4, JSSE, and the SecurityManager.
Either as a servlet initiating an SSL connection to a remote server,
or with Tomcat creating an HTTP Connector which accepts SSL.

To debug these type of problems I recommend the following.

Start Tomcat with the property -Djava.security.debug=access,failure
also for SSL related problems, -Djavax.net.debug=ssl

If you haven't changed your ${java.home}/jre/lib/security/java.security
config security.provider properties, you need to add support for JSSE.

Here are my security.provider properties:

 #
# List of providers and their preference orders (see above):
#
security.provider.1=sun.security.provider.Sun
# Added below for Tomcat 4 SSL support
security.provider.2=com.sun.net.ssl.internal.ssl.Provider
security.provider.3=com.sun.rsajca.Provider

There is also a Security Permission related to use of Certificates.

permission java.security.SecurityPermission "getProperty.cert.provider.x509v1";

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>