You get an error when that's what's occurring, though.
On 12/7/2011 12:55 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jess,
On 12/6/11 6:17 PM, Jess Holle wrote:
Okay, I now notice this plainly stated in the documentation for
JNDIRealm (which I'm using):
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jess,
On 12/6/11 6:17 PM, Jess Holle wrote:
> Okay, I now notice this plainly stated in the documentation for
> JNDIRealm (which I'm using):
>
> The cached user is *not* saved and restored across sessions
> serialisations.
>
> That seems a bit odd
2011/12/7 Mohammad M. AbuZer :
> It should serialize User and Principles nothing more, no need for password.
>
> On Wed, Dec 7, 2011 at 4:12 PM, Konstantin Kolinko
> wrote:
>
>> 2011/12/7 Jess Holle :
>> > I should have noted that this is with Tomcat 7.0.23, but it seemed
>> unlikely
>> > to be JVM
It should serialize User and Principles nothing more, no need for password.
On Wed, Dec 7, 2011 at 4:12 PM, Konstantin Kolinko
wrote:
> 2011/12/7 Jess Holle :
> > I should have noted that this is with Tomcat 7.0.23, but it seemed
> unlikely
> > to be JVM (Java 6 Update 29) or OS (Windows 7) speci
2011/12/7 Jess Holle :
> I should have noted that this is with Tomcat 7.0.23, but it seemed unlikely
> to be JVM (Java 6 Update 29) or OS (Windows 7) specific.
>
> Of course given that I found that the documentation clearly states this
> behavior, I suspect this is longstanding Tomcat behavior.
>
>
Yes, I now note this in the documentation.
The question remains, however: /why /does it work this way?
On 12/7/2011 6:34 AM, Mohammad M. AbuZer wrote:
Tomcat does that for every all Form Authentication even if you used
`DatabaseRealm` it doesn't save logged user.
On Wed, Dec 7, 2011 at 2:24 PM
Tomcat does that for every all Form Authentication even if you used
`DatabaseRealm` it doesn't save logged user.
On Wed, Dec 7, 2011 at 2:24 PM, Jess Holle wrote:
> I should have noted that this is with Tomcat 7.0.23, but it seemed
> unlikely to be JVM (Java 6 Update 29) or OS (Windows 7) specif
I should have noted that this is with Tomcat 7.0.23, but it seemed
unlikely to be JVM (Java 6 Update 29) or OS (Windows 7) specific.
Of course given that I found that the documentation clearly states this
behavior, I suspect this is longstanding Tomcat behavior.
My remaining question is /why/
Jess Holle wrote:
When doing a graceful shutdown of Tomcat, the sessions are persisted to
disk and then re-read on startup (at least in all reasonably recent
versions).
Oddly, however, form-based authentication does not seem to survive a
graceful restart. Rather one has to log in again. Is
Okay, I now notice this plainly stated in the documentation for
JNDIRealm (which I'm using):
The cached user is *not* saved and restored across sessions
serialisations.
That seems a bit odd...
On 12/6/2011 5:12 PM, Jess Holle wrote:
When doing a graceful shutdown of Tomcat, the sessions
When doing a graceful shutdown of Tomcat, the sessions are persisted to
disk and then re-read on startup (at least in all reasonably recent
versions).
Oddly, however, form-based authentication does not seem to survive a
graceful restart. Rather one has to log in again. Is this known?
Inten
11 matches
Mail list logo
