Mel, Mel Rothman wrote: > Increasing the incorrect password count could be a bad thing if it disables >the user > profile. One could argue that the count should be incremented only for an >invalid logon > request and not for a validation request. I respectfully disagree. The API _should_ update the invalid password value because it _is_ a signon. Just because you're not staring at QDSIGNON, doesn't mean that you're not signing on. You're still attempting to access the system as a particular validated user. If you get the password wrong, the Security Officer needs to know about it. If you just want to validate that somone knows some secret password value, use a validation list entry. It can perform validation without exposing the profile to attack. IMHO, jte -- John Earl firstname.lastname@example.org The PowerTech Group --> new number --> 253-872-7788 PowerLock Network Security www.400security.com -- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: email@example.com +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.