All,
I am trying to set up the jmx proxy servlet and am kinda stuck on security.
I would like to:
- restrict access to localhost
- restrict access to require basic authentication
Currently it works, though in the wrong order. This is how the request is
being processed right now:
1) user
with authentication given the order from above?
Any hint for the right direction would be greatly appreciated.
Thanks,
Falco
On Fri, Jul 4, 2014 at 4:37 PM, Falco Schwarz hid...@falco.me wrote:
All,
I am trying to set up the jmx proxy servlet and am kinda stuck on
security. I would like
On Sat, Jul 5, 2014 at 12:39 PM, Mark Thomas m...@homeinbox.net wrote:
Maybe look at a third party security plugin like Spring Security? Not sure if
this is supported but worth a look.
Mark
Thanks Mark and Konstantin for your quick replies. I tried to
accomplish this only using Spring
On Sat, Jul 5, 2014 at 6:17 PM, Hassan Schroeder
hassan.schroe...@gmail.com wrote:
(Sorry, late to the thread but ...) if you just want to restrict access to
a resource to localhost, why not os-level e.g. an iptables rule?
Well, the reason behind the restriction is that I would like to use
Konstantin,
On Sat, Jul 5, 2014 at 3:26 PM, Konstantin Kolinko
knst.koli...@gmail.com wrote:
You can either perform IP filtering in a Valve (that will be in the
pipeline before an Authenticator), or you can remove
security-constraint and implement authentication and authorization in
a filter
On Sun, Jul 6, 2014 at 1:35 PM, Konstantin Kolinko
knst.koli...@gmail.com wrote:
I think you can inject RemoteAddrFilter into Spring Security filter
chain (that is if you do not want to configure it separately in
web.xml),
You are right, I did not think of that.
FWIW this is easily doable
On Tue, Aug 25, 2015 at 5:13 PM, Rainer Jung rainer.j...@kippdata.de
wrote:
Am 25.08.2015 um 14:58 schrieb Falco Schwarz:
If I try to startup httpd though the following error occurs:
httpd: Syntax error on line 88 of /opt/apache/conf/alles/httpd.conf:
Cannot
load /opt/apache/modules
On Wed, Aug 26, 2015 at 8:13 PM, Rainer Jung rainer.j...@kippdata.de
wrote:
I added a configure check in
http://svn.apache.org/viewvc?view=revisionrevision=1697985
and documented the problem in
https://bz.apache.org/bugzilla/show_bug.cgi?id=58285
You might want to cross check.
Hi there,
I tried to update the connectors to the most recent update but I am stuck
with error messages. Just a few background information on the
infrastructure used:
httpd: 2.2.31
OpenSSL: 1.0.2.d
mod_jk: 1.2.41
Kernel: 3.0.101-0.47.52-pae
OS: SLES 11 SP3 (32bit)
gcc: (SUSE Linux) 4.3.4