[JBoss-user] [JNDI/Naming/Network] - Re: Accessing EJB through HTTPS Invoker...

2005-08-30 Thread mc340
Hi, i am working on this problem too. If you have running JNDI over HTTPS and EJB over HTTP it's only a small step to have EJB over HTTPS too. Now i'm running JNDI and EJB over a single HTTPS port(8443). So far so good. But now the connection is VERY, VERY slow, it's not usable anymore. I don't

[JBoss-user] [JNDI/Naming/Network] - Re: Accessing EJB through HTTPS Invoker...

2005-08-29 Thread benoitx
Hi Oliver Thanks for your reply (only read it today,...just back from a few days off...) It looks very promising, I will try your solution and try to use HTTPs with it. I shall report my findings here! regards from London Benoit View the original post : http://www.jboss.org/index.html?module

[JBoss-user] [JNDI/Naming/Network] - Re: Accessing EJB through HTTPS Invoker...

2005-08-29 Thread martinh
Hi, i don't kno wif this could help, but i've a JBoss behind a Firewall, i'm using JNDIFactory (JNDI over HTTP) and there is no documentation abot this, you have to open the port in your firewall pointing to Jboss server, i didn't know that, i've noticed scanning the port acces while trying

[JBoss-user] [JNDI/Naming/Network] - Re: Accessing EJB through HTTPS Invoker...

2005-08-22 Thread Olli_Ger
Hello, I just got it working: Access EJBs and the JNDI via HTTP. I'm, able to access the Enterprise Beans via ONE PORT. My advices are of course without warranty! ;-) I think Benoit is right, the scenario specified allows only JNDI via http(s). Remember, in my requirements HTTP is all right! You

[JBoss-user] [JNDI/Naming/Network] - Re: Accessing EJB through HTTPS Invoker...

2005-08-08 Thread miani
Benoit, That is great that you got it working. But, we had already gotten RMI over SSL working. I just don't see much value to it (at least for us) unless you can actually tunnel the packets over port 443. Even if I could get them to agree to it, I don't feel comfortable advising my customers t

[JBoss-user] [JNDI/Naming/Network] - Re: Accessing EJB through HTTPS Invoker...

2005-08-06 Thread benoitx
Hi Jim & all, Following my previous post, I got it to work by opening port (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

[JBoss-user] [JNDI/Naming/Network] - Re: Accessing EJB through HTTPS Invoker...

2005-08-05 Thread miani
Benoit, I've been fighting the same issue. Encrypting the EJB calls with SSL is nice but what's the point if you can't go over https? Customers aren't going to open a bunch of ports on their firewall for us. Anyway, I couldn't have typed up your post better myself. Anyone out there have an e