anonymous wrote : But they should neither be allowed to open the start page of JBoss (with all the Tomcat stats and so on),
Some ways to do this:
1) Remove that application from being deployed (but that would mean even you cannot access it).
2)
2.a) Don't let it be the root application and instead setup your application as the root application http://www.jboss.org/community/docs/DOC-12261
2.b) Secure the ROOT.war application which shows the JBoss home page with password protected access (same as securing the jmx-console that i pointed out in my previous reply).
anonymous wrote : especially not the jmx console and the web console.
Same approach as above.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221768#4221768
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221768
anonymous wrote : What I am thinking I will do is to have two seperately built WAR files, one for production, and one for deployment. And each of them have seperate property files and different Jndi bindings so they can be deployed along side each other on the same Application server.
That would be too much of work and you could even end up messing up the production application's data (imagine pointing to the prod DB datasource in your dev application).
The question really is:
1) Do you want both the dev and the prod application on the same server? If not, then you can host it on a separate dev system (which is the most common way for such things).
2) Do you want them to be running simultaneously?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221767#4221767
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221767
Thank you for your answer!
I want all users except one IP to be only allowed to access http://my-jboss-server.net:8080/myApplication.
Only the given IP address (my proxy) is allowed to open the root page http://my-jboss-server.net:8080, the jmx console and the web console.
What I am trying to get: I want to publish my project on my server that is globally accessible. Everybode should be able to access my application that is published on the JBoss AS. But they should neither be allowed to open the start page of JBoss (with all the Tomcat stats and so on), nor should they open anything else but my project - especially not the jmx console and the web console. They should only be able to open my project. Nothing else.
How do I realize that best?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221766#4221766
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221766
Hi!
I am new to JBoss. A few months ago I started to familiarize myself with JBoss Seam and JSF and just finished my first "really" web application that I want to put on my productive server, where I put on a jboss-4.2.3.GA, to test the project under "real life conditions".
Nevertheless, the deployment worked as it should but I don't know how to secure the administration (jmx-console, web-console) and the JBoss Startup screen (with the link to TomCat stats etc).
Is there an easy way to bind it to my (static) IP adress, so that access from another ip is rejected? Additional is there a way to (IP based) reject access to any other url of JBoss than http://my-server.net:8080/myProject/?
I know that this won't be a perpertual solution, but in the meantime I'm going to be a book to learn how to properly administrate the JBoss AS.
Could you recommend me a good book about JBoss AS administration?
Thank you in advance!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221762#4221762
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221762
I found I must include the JBOSS_HOME\client\jbossall-client.jar into the client's classpath. But previously I copied the jbossall-client.jar from JBOSS_HOME\client to my Myeclipse project, and includes this copy to my client's classpath, this dosen't work.
Can anybody explain why I must include the JBOSS_HOME\client\jbossall-client.jar instead of a copy? In an application, normally the client wouldn't be at the same machine as the server, so the client couldn't include the jbossall-client.jar at the server side, that's why I made a copy of jbossall-client.jar from the server.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221759#4221759
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221759