with all that said, I think the best option for you is to
- create an extension of the current realm instead of patching the
existing one
- submit the code
- and if everyone thinks its useful, the code looks good, we can add it
to Tomcat and let the user decide if they wanna use it
but I don'
Those are very valid questions.
1. Yes so i guess there could be a default value in the code so that
it could always be set to 3 unless
set by the admin.
2. I am not sure how to handle this, as if you only had read access
to the database then there would be no
way to set this up, unl
sounds like a useful feature, are you considering
1. That the feature must be 100% backwards compatible, ie work if they
dont specify the column or the column doesn't exist
2. That some database admins might only give you a read only connection,
so the column exists but is not writable
3. How
All
I am trying to improve the security for authenticating users on my
JDBC realm. What we require is the ability to lock out accounts on
the database
when a user enters more than 3 incorrect passwords. Now i have made
some changes to the JDBCRealm.java and i would like some comments
on the
