--- "Ignacio J. Ortega" <[EMAIL PROTECTED]> wrote:
> > De: Jim Seach [mailto:[EMAIL PROTECTED]]
> > Enviado el: jueves 7 de marzo de 2002 18:08
>
> >
> > A new feature, but a suggestion rather than a request. Even if the
> > client realm doesn't support Digest authentication, we can
> > use B
> De: Jim Seach [mailto:[EMAIL PROTECTED]]
> Enviado el: jueves 7 de marzo de 2002 18:08
>
> A new feature, but a suggestion rather than a request. Even if the
> client realm doesn't support Digest authentication, we can
> use Basic or
> Form to get the user ID and password in the clear, then
all,
john
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
g]On Behalf Of Jim Seach
Sent: Thursday, March 07, 2002 9:38 AM
To: Tomcat Developers List
Subject: RE: [PATCH] change JDBCRealm to add flexibility in table layout
Ignacio,
I apologize for not reading more
--- "Ignacio J. Ortega" <[EMAIL PROTECTED]> wrote:
> > De: Jim Seach [mailto:[EMAIL PROTECTED]]
> > Enviado el: jueves 7 de marzo de 2002 16:38
>
> >
> > Ignacio,
> >
> > I apologize for not reading more closely. You didn't -1 it, just
>
> And i apologize everybody for writing english so bad
> De: Jim Seach [mailto:[EMAIL PROTECTED]]
> Enviado el: jueves 7 de marzo de 2002 16:38
>
> Ignacio,
>
> I apologize for not reading more closely. You didn't -1 it, just
And i apologize everybody for writing english so bad :),
> expressed your opinion. I agree your proposed changes would
Ignacio,
I apologize for not reading more closely. You didn't -1 it, just
expressed your opinion. I agree your proposed changes would be much
more flexible. Another option that might be nice would be the ability
to specify a user supplied class to compute a password hash so only the
hash needs
> De: Jim Seach [mailto:[EMAIL PROTECTED]]
> Enviado el: jueves 7 de marzo de 2002 14:16
>
> Ignacio,
>
> Forgive me if I don't understand, but it appears you are saying that
> JDBCRealm's use of a sub-optimal table design is *flexible* because
> there are ways in some databases to modify a cor
Ignacio,
Forgive me if I don't understand, but it appears you are saying that
JDBCRealm's use of a sub-optimal table design is *flexible* because
there are ways in some databases to modify a correct schema (by adding
a view) to make it work with JDBCRealm? It seems to me in this case
that it is
> De: John Gregg [mailto:[EMAIL PROTECTED]]
> Enviado el: miƩrcoles 6 de marzo de 2002 15:26
> provided, but I consider it an improvement nonetheless because I value
> flexible designs. I would expect the MySQL users to
a flexible design is what you get in JDBCREalm, dont misinterpret me,
the
7;ll confine myself to
> ordinary bug fixes and not design "improvements."
>
> john
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> g]On Behalf Of Ignacio J. Ortega
> Sent: Tuesday, March 05, 2002 1:43 PM
> To: 'T
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
g]On Behalf Of Ignacio J. Ortega
Sent: Tuesday, March 05, 2002 1:43 PM
To: 'Tomcat Developers List'; '[EMAIL PROTECTED]'
Subject: RE: [PATCH] change JDBCRealm to add flexibility in table layout
( Syntax aprox
> De: John Gregg [mailto:[EMAIL PROTECTED]]
> Enviado el: martes 5 de marzo de 2002 20:11
> I don't see how views will solve this problem. I'm not so
> much concerned
> with reading user and role data as I am with updating it.
> Somehow the two
> tables need to be linked by some common identi
opers List'; '[EMAIL PROTECTED]'
Subject: RE: [PATCH] change JDBCRealm to add flexibility in table layout
Why do not use simply a views, instead of real tables..??
This way you doesnt need to do any changes in JDBCRealm to be able to
use whatever column you like to join roles and users t
> De: John Gregg [mailto:[EMAIL PROTECTED]]
> Enviado el: martes 5 de marzo de 2002 1:27
> in the layout of one's users and roles tables. The current
> implementation
> (1.20) assumes the roles table will have a column with the
> same name and
> meaning as the username column in the users tabl
Hi all.
I'd like to propose a change to JDBCRealm to allow a little more flexibility
in the layout of one's users and roles tables. The current implementation
(1.20) assumes the roles table will have a column with the same name and
meaning as the username column in the users table. In general,
15 matches
Mail list logo