You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2004/10/18 04:48:43 UTC
DO NOT REPLY [Bug 31753] New: -
inconsistency in #authenticate(Connection, ...) for JDBCRealm and DataSourceRealm
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31753>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31753
inconsistency in #authenticate(Connection, ...) for JDBCRealm and DataSourceRealm
Summary: inconsistency in #authenticate(Connection, ...) for
JDBCRealm and DataSourceRealm
Product: Tomcat 5
Version: Nightly Build
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: shinobu.kawai@gmail.com
I couldn't help noticing the inconsistency in #authenticate(Connection, String,
String) for JDBCRealm and DataSourceRealm.
- Getting dbCredentials
JDBCRealm:
if (rs.next()) {
dbCredentials = rs.getString(1);
}
DataSourceRealm:
while (rs.next()) {
dbCredentials = rs.getString(1);
}
- Getting roles
JDBCRealm:
while (rs.next()) {
String role = rs.getString(1);
if (null!=role) {
roleList.add(role.trim());
}
}
DataSourceRealm:
while (rs.next()) {
list.add(rs.getString(1).trim());
}
I think the JDBCRealm approach is better in both cases.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
RE: DO NOT REPLY [Bug 31753] New: -
Posted by Gary Youssef <ga...@royallinksusa.com>.
remove!
Gary Youssef
National Sales Manager
Royal Links USA
"The Advertising & Hospitality Vehicle"
800.908.6937 X 321
419.944.9007 Mobile
888.766.1879 Toll Free Fax
garyy@royallinksusa.com
www.royallinksusa.com
-----Original Message-----
From: bugzilla@apache.org [mailto:bugzilla@apache.org]
Sent: Sunday, October 17, 2004 10:49 PM
To: tomcat-dev@jakarta.apache.org
Subject: DO NOT REPLY [Bug 31753] New: -
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31753>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31753
inconsistency in #authenticate(Connection, ...) for JDBCRealm and
DataSourceRealm
Summary: inconsistency in #authenticate(Connection, ...) for
JDBCRealm and DataSourceRealm
Product: Tomcat 5
Version: Nightly Build
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: shinobu.kawai@gmail.com
I couldn't help noticing the inconsistency in #authenticate(Connection,
String,
String) for JDBCRealm and DataSourceRealm.
- Getting dbCredentials
JDBCRealm:
if (rs.next()) {
dbCredentials = rs.getString(1);
}
DataSourceRealm:
while (rs.next()) {
dbCredentials = rs.getString(1);
}
- Getting roles
JDBCRealm:
while (rs.next()) {
String role = rs.getString(1);
if (null!=role) {
roleList.add(role.trim());
}
}
DataSourceRealm:
while (rs.next()) {
list.add(rs.getString(1).trim());
}
I think the JDBCRealm approach is better in both cases.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org