Sorry a mistake, without transport guarantee, container managed security
will not work at all.. constraints need to have transport to be added to
context.
Saludos ,
Ignacio J. Ortega
> -----Mensaje original-----
> De: Ignacio J. Ortega [mailto:[EMAIL PROTECTED]]
> Enviado el: martes 6 de marzo de 2001 1:07
> Para: '[EMAIL PROTECTED]'
> Asunto: RE: JDBC Realm not triggering
>
>
> A wild thought, try with uppercase for methods GET,POST and so on, i
> think code is doing equals not equalsignorecase.
> > - If I omit <transport-guarantee>, does it default to NONE?
> >
>
> yes..
>
> > - I would like to use a numeric column in the database to
> > store the user
> > authentication level, rather than a text string. Can the
> > JDBC realm be set
> > up to work this way, or must I subclass a new realm class?
>
> Simply using numeric roles , JDBCRealm should work without problems.
>
> > - Is it possible to use * for <http-method> to specify
> that all HTTP
> > methods are to be subject to security?
>
> No AFAIK,
>
> > - Another participant in this listserv mentioned that TomCat
> > 3.2.1's JDBC
> > realm doesn't use connection pooling. Any idea if TomCat 4.x
> > will implement
> > this? I want to support a high traffic site, and without
>
> for 3.3 & 4.0 it's on my todo list from now..
>
> Please file a RFE on http://nagoya.apache.org/bugzilla against 4.0 and
> 3.x versions of tomcat.
>
> TIA
>
> Saludos ,
> Ignacio J. Ortega
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
