[JBoss-user] [Security JAAS/JBoss] - Re: RMI ports and firewall

2005-01-27 Thread henkie
3 short steps to make jboss accessible from outside firewall, presuming on windows ( for step 3 ): 1. Make sure you have a name resolving to the external IP address of the FW eg.: externalip.example.org 2. Startup the JBoss server with an extra parameter: -b externalip.example.org 3. Supposing

[JBoss-user] [Security JAAS/JBoss] - Re: RMI ports and firewall

2005-01-19 Thread schrouf
We have a working RMI firewall configuration with the following enabled ports TCP:1099 (JNDI Naming) TCP:1100 (Cluster JNDI Naming) TCP:1098 (RMI-Port) TCP: (RMI-Object-Port) Regards Ulf View the original post :

[JBoss-user] [Security JAAS/JBoss] - Re: RMI ports and firewall

2005-01-19 Thread SebastianG
Hi, it's me again. I am still stuck in that problem. I also searched several other forums for that issue and whever I found it I couldn't get a satisfying answer. I even read somewhere that it is a general Java RMI issue that one cannot get around. Is that true? It would be really helpful

[JBoss-user] [Security JAAS/JBoss] - Re: RMI ports and firewall

2004-12-28 Thread SebastianG
Hi, I have exactly the same problem when trying to connect to jboss through a firewall. I configured my jboss 3.2.6 server as mentioned on the Wiki. Here is my client code: Hashtable env = new Hashtable(); env.put(Context.PROVIDER_URL, myServer:1099); env.put(Context.INITIAL_CONTEXT_FACTORY,

[JBoss-user] [Security JAAS/JBoss] - Re: RMI ports and firewall

2004-06-02 Thread firebirth
Hello again, I finally figured out what it takes to restrict rmi communication between jboss app server and servlet engine to one specific port, in this case to . I had to uncomment the following line in the jboss-service.xml file, section rmi/jrmp invoker: attribute

[JBoss-user] [Security JAAS/JBoss] - Re: RMI ports and firewall

2004-05-26 Thread vombi
I don't see the answer on the wiki page - maybe the question was not clear enough: The ejb client is on the servlet/web server machine and makes a ejb lookup and connection to a separate machine running JBoss. This causes the high random listening ports to appear at run/invokation time. In fact

[JBoss-user] [Security JAAS/JBoss] - Re: RMI ports and firewall

2004-05-24 Thread [EMAIL PROTECTED]
jnp.properties is no longer used. See the referenced wiki page. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3836115#3836115 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3836115

[JBoss-user] [Security JAAS/JBoss] - Re: RMI ports and firewall

2004-05-21 Thread firebirth
Thanks, Adrian. But I don't really feel satisfied yet. I would like to be more precise: We have a stand-alone app server (JBoss 3.2.3) and a stand-alone servlet engine (Tomcat 5.0.19). These two components should be separated by a firewall. From what I found on the Wiki (the one you suggested)

[JBoss-user] [Security JAAS/JBoss] - Re: RMI ports and firewall

2004-05-21 Thread [EMAIL PROTECTED]
Check again: http://www.jboss.org/wiki/Wiki.jsp?page=UsingJBossBehindAFirewall View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3835843#3835843 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3835843