[Craig]
Sounds like you really should write a custom
Authenticator that doesn't
use the standard Realm back end. Nothing requires
you to do that --
and,since you'd need a custom Realm anyway, you might
as well just combine
everything into a single class.
Of course I can do this, but it looks as
I'm having problems using the Tomcat 4 security design for a slightly
customised requirement. I've created a custom realm for an external
information provider which, when I authenticate a user, gives me a token (in
the form of an essentially opaque object). This token needs to be passed
back to
On Fri, 25 Oct 2002, vsajip (yahoo.com) wrote:
Date: Fri, 25 Oct 2002 23:06:29 +0100
From: vsajip (yahoo.com) [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Problems with Tomcat4 Security Design
I'm having problems using the Tomcat 4
I'm having problems using the Tomcat 4 security design for a slightly
customised requirement. I've created a custom realm for an external
information provider which, when I authenticate a user, gives me a token (in
the form of an essentially opaque object). This token needs to be passed
back to
