Re: Where are FAILED_LOGIN_ATTEMPTS recorded?

From: <fitzjarrell_at_cox.net>
Date: 16 Oct 2007 11:13:36 -0700
Message-ID: <1192549117.472141.51220@q3g2000prf.googlegroups.com>

On Oct 16, 10:04 am, "deebe..._at_gmail.com" <deebe..._at_gmail.com> wrote:
> Hi,
>
> Using 10gR2 - trying to find out where FAILED_LOGIN_ATTEMPTS are
> recorded.

I doubt you'll find it stored anywhere.

> FAILED_LOGIN_ATTEMPTS is currently set to 10 as per the Default
> profile.
>
> There is no auditing in place but failed logins for users must be
> recorded somewhere (ie internal table) for the profile to work.

Why? Consider this:

SQL> set serveroutput on size 1000000
SQL>
SQL> declare
  2     login_trys number;
  3     cursor get_failed_login_lim is
  4     select limit
  5     from dba_profiles
  6     where resource_name = 'FAILED_LOGIN_ATTEMPTS'
  7     and limit <> 'UNLIMITED';
  8  begin
  9     open get_failed_login_lim;
 10     fetch get_failed_login_lim into login_trys;
 11     close get_failed_login_lim;
 12
 13     for tries in 1..6 loop
 14             if tries > login_trys then
 15                     dbms_output.put_line('BZZZZZZT!!!! Account
locked!!!');
 16             else
 17                     dbms_output.put_line('Keep trying ...');
 18             end if;
 19     end loop;

 20 end;
 21 /

Keep trying ...
Keep trying ...
Keep trying ...
Keep trying ...
Keep trying ...

BZZZZZZT!!!! Account locked!!!

PL/SQL procedure successfully completed.

SQL> Try to find login_trys in the database; it isn't there, yet the mechanism works as expected. The only value which needs to be in a table/view is the limit which is set. The code processing the logins can record the unsuccessful attempts and call the appropriate code to lock the account once the limit has been exceeded.

>
> Cheers
> D

David Fitzjarrell Received on Tue Oct 16 2007 - 13:13:36 CDT