Issue Details (XML | Word | Printable)

Key: OPENEJB-785
Type: New Feature New Feature
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Kazem Naderi
Reporter: David Blevins
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
OpenEJB

EJBd protocol over SSL

Created: 27/Mar/08 06:47 PM   Updated: 24/Jun/08 02:00 AM
Return to search
Component/s: security, server
Affects Version/s: 3.0-beta-1, 3.0-beta-2
Fix Version/s: 3.1

Time Tracking:
Not Specified

File Attachments:
  Size
Zip Archive Licensed for inclusion in ASF works openejb-client.zip 2008-04-16 06:08 PM Kazem Naderi 792 kB
Zip Archive Licensed for inclusion in ASF works openejb-server.zip 2008-04-16 06:10 PM Kazem Naderi 344 kB
Text File Licensed for inclusion in ASF works simplified-ssl.txt 2008-04-29 05:21 AM David Blevins 5 kB

Resolution Date: 12/May/08 11:05 PM


 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Kazem Naderi added a comment - 16/Apr/08 06:08 PM
Unzip this file into the Server folder to replace openejb-client.

The changes you will see are:
New imprt statemant in ConnectionManager.java
New org.apache.openejb.client.socket package

Kazem Naderi added a comment - 16/Apr/08 06:10 PM
Unzip this file into the Server folder to replace openejb-server.

The changes you will see are:
ServiceDaemon.java
New org.apache.openejb.server.socket package

Kazem Naderi added a comment - 16/Apr/08 06:26 PM
Please see the two attached zip files.

Since I have never been able to run openejb build successfully on my machine I cannot verify that my changes do not introduce any build failures. On eclipse everything is fine and my unit tests pass. This is why I have not checked in my changes and have attached them to this Jira Item.

I added some implementation to openejb-client and openejb-server where it allows using either normal Socket tor SSLSocket.

On the server side the ServerDaemon.java checks for a "secure" property value. If the value is true then it will create an SSLServerSocket and SSLServerSocketConnectionListener for communication, otherwise it behaves as it was before.

On the client side the SocketConnectionFactory again checks for the "secure" property value to decide whether to create an SSLSocketConnection or normal SocketConnection.

How to integrate this with the rest of the system(Geranimo,...) I am not sure. I do not think this should be difficult. My changes are very modular and self-contained.


Getting these changes and without introducing the new property for secure connection, openejb should work as it has been before and default to creating normal Sockets on both client and server.

I appreciate your feedback and please let me know how I can help to get this introduced to the latest release.

David Blevins added a comment - 12/May/08 11:05 PM