-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ravi,
On 3/3/14, 5:53 PM, Ravi Gupta wrote:
Any idea if the same would work for JBOSS 5.X (uses tomcat under
the hood)? perhaps it is not the same, but I tried putting
admin-console.xml under
jboss-5.1.0.GA/server/default/deploy/jbossweb.sar
Tomcat 6.X
RHEL
I tried adding the below in order to limit access to /admin-console
It worked, but it limits access to EVERY context, which is odd. I am sure I
am doing something wrong or I misunderstand how this works
I want to put restrictions on the /admin-console context, but I do not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ravi,
On 3/3/14, 5:10 PM, Ravi Gupta wrote:
Tomcat 6.X RHEL
I tried adding the below in order to limit access to
/admin-console
It worked, but it limits access to EVERY context, which is odd. I
am sure I am doing something wrong or I
Thanks, the issue is that my customer does not want to restrict the
admin-console in it's war - the rational is anybody can then just redeploy
a new admin-console.war and access it (overwrite the restrictions). They
want to restrict access to this context from OUTSIDE the actual deployment.
Make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ravi,
(Moving the discussion back onto the list: please reply to the list
and not to individuals. That's what community is about.)
On 3/3/14, 5:29 PM, Ravi Gupta wrote:
Thanks, the issue is that my customer does not want to restrict
the
Any idea if the same would work for JBOSS 5.X (uses tomcat under the hood)?
perhaps it is not the same, but I tried putting
admin-console.xml under jboss-5.1.0.GA/server/default/deploy/jbossweb.sar
it contains
Context path=/admin-console
Valve className=org.apache.catalina.valves.RemoteAddrValve
According to this, it should match up
https://community.jboss.org/wiki/Web-AppContextConfiguration
On Mon, Mar 3, 2014 at 4:53 PM, Ravi Gupta rkgupt...@gmail.com wrote:
Any idea if the same would work for JBOSS 5.X (uses tomcat under the hood)?
perhaps it is not the same, but I tried putting
