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=30743>.
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=30743

Custom <Realm> attributes handled differently in 5.0.27.

           Summary: Custom <Realm> attributes handled differently in 5.0.27.
           Product: Tomcat 5
           Version: 5.0.27
          Platform: All
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


To implement a custom login attempt counter I extended the DataSourceRealm 
class in 5.0.19 & 5.0.25. Several extra attributes were added to the standard 
<Realm> element in the applications context.xml eg.

  <Realm 
    className="mypkg.MyDataSourceRealm" 
    dataSourceName="jdbc/ebira" 
    debug="99" 
    localDataSource="true" 
    maxLoginAttempts="3" 
    roleNameCol="role" 
    userCredCol="pwd" 
    userInvalidCountCol="invalidCount" 
    userNameCol="userid" 
    userRoleTable="userRole" 
    userTable="person"/>

My custom realm class subclassed DataSourceRealm & had fields to store the 
additional attributes. This worked fine in 5.0.19 & 5.0.25.

For some reason a change has been made in 5.0.27 that prevents the setter 
methods for the additional attributes from being invoked. eg. setUserTable is 
still invoked but setMaxLoginAttempts is not.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to