-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lb,
lightbulb432 wrote:
> Anytime I want to use more than two credentials, I have to provide my
> own Realm implementation. But the only time I need to do the String
> concatentation is when at least one of the additional credentials
> (i.e. beyond u
Wow, those are good suggestions. I was thinking about the String
concatenation, but didn't think it was worth considering further until you
just mentioned it. So let me see if I have this straight:
Anytime I want to use more than two credentials, I have to provide my own
Realm implementation. But
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lb,
lightbulb432 wrote:
> Views would definitely allow me to keep the two tables separate, but then I'd
> have to authenticate against the two source tables separately (i.e. each
> application would point to the source table rather than to the view).
Views would definitely allow me to keep the two tables separate, but then I'd
have to authenticate against the two source tables separately (i.e. each
application would point to the source table rather than to the view). If
pointing both applications to the common view, then doesn't the original
p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lb,
lightbulb432 wrote:
> The requirement doesn't accept having two tables (i.e. userTableA and
> userTableB), partly because increased maintenance, the possibility of table
> definitions going out of sync, etc.
CREATE VIEW, anyone?
- -chris
-B
Here's the case where three credentials are necessary: there is a requirement
to host multiple applications on a single database, and data such as users
are in a single, shared table. Therefore, someone logging into app A would
enter username and password of user1 and pass1, and someone else loggi
well, we can't tell you the whole desigh of your_app-to-be but gave
you some starting-points. now it's up to you to use them.
however, i do not see any sense at all passing more tha two
credentials (user, pass) to authenticate
therefore, i suggest first thing you should do is to re-think the
I took a look at JAASRealm and its authenticate method only takes two
parameters (username and "credentials", which is really just a single
password string).
Is it possible to pass my other credentials to the JAASRealm so that I can
pass everything at one time (username, password, other credentia
at least you've saved *half* of the time ;)
cheers
greg
--
what's puzzlin' you, is the nature of my game
gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2
gpgp-key available @ http://pgpkeys.pca.dfn.de:11371
-
To start a new to
Gregor Schneider wrote:
Well, subclassing FormAuthenticator would be a hack, a
Tomcat-only-solution and inho a bad one.
therefore, take a look at JAASRealm and try to combine it with your
existing login-procedure, meaning
- Implement a JAASRealm
- get the credentials from there (user, password)
Well, subclassing FormAuthenticator would be a hack, a
Tomcat-only-solution and inho a bad one.
therefore, take a look at JAASRealm and try to combine it with your
existing login-procedure, meaning
- Implement a JAASRealm
- get the credentials from there (user, password)
- do the JAAS-Authentica
I'll try to avoid the hack method if possible.
Let me clarify the two requirements that my authentication process must
meet. It must use an existing stored procedure that will return a login
success/fail response, and it needs additional credentials (username,
password, and at least one other fie
in $CATALINA_HOME/server/lib/catalina.jar there's a file "catalina.properties".
There your will find the following entries:
BASIC=org.apache.catalina.authenticator.BasicAuthenticator
CLIENT-CERT=org.apache.catalina.authenticator.SSLAuthenticator
DIGEST=org.apache.catalina.authenticator.DigestAuth
Thanks for pointing me to that class. How can I specify my overriden version
in a configuration file or programmatically so that it can be used?
Also, I was looking into how to solve the problem from my original post, and
came across the concept multiple times of providing my own Realm
implementa
You could call the authenticate()-method from Tomcat's FormAuthenticator:
http://tomcat.apache.org/tomcat-5.0-doc/catalina/docs/api/org/apache/catalina/authenticator/FormAuthenticator.html#authenticate(org.apache.catalina.HttpRequest,%20org.apache.catalina.HttpResponse,%20org.apache.catalina.depl
15 matches
Mail list logo