tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 16316] - DataSourceRealm can not find JNDI name in context
Date Thu, 12 Jun 2003 05:11:50 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16316>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16316

DataSourceRealm can not find JNDI name in context





------- Additional Comments From dan@mojavelinux.com  2003-06-12 05:11 -------
I would like to second this last suggestion.  The bug became apparent to me when
I was using securityfilter to complete container-like managed security.  At
first I thought the bug was in securityfilter, but after breaking it back down
to container managed security, I still could not avoid an exception being thrown
due to the JNDI context not being available.  I could obtain a connection to the
datasource using the test case in the realm docs for Tomcat, but not when trying
to use container managed security.  After copying DataSourceRealm to my own
package, changing the lines recommended in the previous post and using the
result, I could authenticate my user.  This is clearly a huge bug rendering the
DataSource realm impossible to use in a specified context.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message