Thank you, Martin, for answering despite of the messed up email!
A short point to clarify: I am using JAASRealm, and a custom jaas.config file
which does not refer to AASMemoryLoginModule. So JAASMemoryLoginModule is also
not called.
As for my custom login module, I checked it, and it does
So this is interesting.
So from HTTP server #1 (172.1.1.1 example) I hit:
https://172.1.1.1:23270/static and I see this in the HTTP log:
172.1.1.1 - - [22/Feb/2017:10:14:48 -0800] "GET /static/ HTTP/1.1" 200 32
I see this in the Tomcat log:
172.1.1.1 - - [22/Feb/2017:10:14:48 -0800] "GET /static/
Dear Martin,
On 21/02/17 13:31, Martin Knoblauch wrote:
Hi,
is there a way to find the absolute path of the application root before
the servlet is initialized?
Alternatively: is there a way to defer the initialization of a datasource
until the servlet is initialized?
Background: I have
Am 22.02.2017 um 11:19 schrieb Martin Knoblauch:
On Tue, Feb 21, 2017 at 8:55 PM, Mark Thomas wrote:
On 21/02/2017 13:31, Martin Knoblauch wrote:
Hi,
is there a way to find the absolute path of the application root before
the servlet is initialized?
Alternatively: is
On Tue, Feb 21, 2017 at 8:55 PM, Mark Thomas wrote:
> On 21/02/2017 13:31, Martin Knoblauch wrote:
> > Hi,
> >
> > is there a way to find the absolute path of the application root before
> > the servlet is initialized?
> >
> > Alternatively: is there a way to defer the
(noticed that my previous post on the same was somewhat garbled - reposting
reformatted) Hi, I am playing around with the following things: - X.509
authentication- Security Manager enabled- Custom JAAS login module via
JAASRealm My custom JAAS login module properly propagates a