Hi Jim & all, Following my previous post, I got it to work by opening port 4444 (the RmiObject port).
I guess that the scenario specified above allow only JNDI access via HTTPs but the RMI is not encrypted. I then have setup RMI over SSL without too much trouble (see Chap 8 of the Jboss Admin & Dev guide). And, yes you will require a port to be open 14445 in the example. The trick is that the client application MUST have access to a trustore if your server certificate is self-signed. You may want to create your public/private keys then export the X509 certificate and then import it in another keystore and distribute that one instead of the original (as it would only contain the public key through the certificate). I can post a bit more if you want. Best regards from London (yeah, then English one) Benoit View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3888747#3888747 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3888747 ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
