seems.
-Original Message-
From: Gregor Schneider [mailto:rc4...@googlemail.com]
Sent: Sunday, February 22, 2009 3:12 PM
To: Tomcat Users List
Subject: Re: Authenticating Users
To the OP:
1. May I ask what database it is you're using?
2- I'd go for the following solution:
Cr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin,
Wow.
On 2/22/2009 8:52 PM, Martin Gainty wrote:
>> Alan Chaney wrote:
>>
>> To summarize
>>
>> 1. password be case insensitive [I may be able to talk them out of this]
> MG>handled from java.lang.String toUpperCase/toUpperCase
> http://java.s
>
> Martin Gainty wrote:
> > Which specific attributes are you seeking that are not in DataSourceRealm?
> > >dataSourceName="jdbc/authority"
> >userTable="users" userNameCol="user_name" userCredCol="user_pass"
> >userRoleTable="user_roles" roleNameCol="role_name"/>
> > http://tomcat.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan,
On 2/22/2009 4:47 PM, Alan Chaney wrote:
> From my point of view, as I don't use hashed passwords at the moment the
> easiest thing to do is to modify the DataSourceRealm as suggested by
> Mark Thomas. However, I think that the ability to extend
Martin Gainty wrote:
Which specific attributes are you seeking that are not in DataSourceRealm?
http://tomcat.apache.org/tomcat-5.5-doc/realm-howto.html#DataSourceRealm
?
To summarize
I (or,actually my "marketing dept') have the following requirements.
1. password be case insensitive [I
800
> From: a...@compulsivecreative.com
> To: users@tomcat.apache.org
> Subject: Re: Authenticating Users
>
> Gregor Schneider wrote:
> > To the OP:
> >
> > 1. May I ask what database it is you're using?
> >
> Postgres - but a more general solut
Gregor Schneider wrote:
To the OP:
1. May I ask what database it is you're using?
Postgres - but a more general solution would be nice.
2- I'd go for the following solution:
Create a JSP-page accepting the credentials. The username should be
converted to uppercase. The password should be l
(function() {
var doLogin = function() {
var uname = doc.byId("name").toLowerCase();
var passw = doc.byId("password").toLowerCase();
//var digest = sha1.digest(uname + ":My Realm:" + passw);
xhr.send(...);
}
return {
login: function() {
doLogin();
return false
To the OP:
1. May I ask what database it is you're using?
2- I'd go for the following solution:
Create a JSP-page accepting the credentials. The username should be
converted to uppercase. The password should be left as is so that
case-sensivity here is maintained.
Don't know if I'm missing some
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
I was the OP on this one. Mark just made a couple of suggestions.
On 2/21/2009 4:06 PM, Mark Thomas wrote:
5. Patch DataSourceRealm
6. Make case sensitivity configurable and contribute your patch back to
th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 2/21/2009 4:06 PM, Mark Thomas wrote:
> 5. Patch DataSourceRealm
>
> 6. Make case sensitivity configurable and contribute your patch back to
> the ASF.
7. Use securityfilter to write your realm, and not be tied to Tomcat.
8. Many databases
Mark Thomas wrote:
5. Patch DataSourceRealm (should just be a couple of changes to make the
checks case insensitive) and deploy your patched version to each of your
Tomcat instances. To do this you'd put your DataSourceRealm.class file
in CATALINA_HOME/lib/org/apache/catalina/realm
6. Make cas
Alan Chaney wrote:
> We have a site which has users log in to create/edit account
> information. Nothing unusual there. Currently this is implemented with a
> JDBCRealm and it all works OK.
I'd base your solution on the DataSourceRealm. JDBCRealm is very heavily
synchronised .
> So far, I can see
13 matches
Mail list logo
