|
| Problem | What is needed to have Enterprise JavaBeans™ (EJB™) or servlets be Secured Sockets Layer (SSL) clients to a totally separate SSL secured server? | | Cause | It is possible to write enterprise beans and servlets that can be accessed only through a separate SSL secured server, such as an SSL client. The HTTPS URL Connection handlers for the java.net.URLConnection class are not shipped with WebSphere® Application Server 3.5.x. The SSLight classes are internal to WebSphere Application Server and are not supported for external use, and there is no supporting documentation.
For WebSphere Application Server V3.5.x, our official stance is to treat JSSE and other extensions (JCE, and others) that are not included with WebSphere Application Server 3.5.x as third party software.
Since WebSphere Application Server V3.5.x is out of support, no defects will be accepted; you are encouraged to migrate to a supported version of WebSphere Application Server. | | Solution | For WebSphere Application Server 3.0.2.x and 3.5.x, a third party Java™ SSL toolkit is required (such as, RSA's SSL-J).
For WebSphere Application Server 4.0.x, Java Secured Socket Extension (JSSE) support is not available | |
| |
| |
|
Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Security Operating system(s): Multi-Platform Software version: 3.5, 4.0 Software edition: Advanced, Standard Reference #: 1000552 IBM Group: Software Group Modified date: 2004-09-23
(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
|