|
|
|
|
Re: How to trace which user causing the account lock [message #261000 is a reply to message #255465] |
Tue, 21 August 2007 08:40 |
kafaween
Messages: 7 Registered: August 2007 Location: Jordan
|
Junior Member |
|
|
Hi
I have a similar problem , my environment is a 3-tier architecture , i.e. all users connect to DB via Application server , i activate audit_trail to 'DB' , but when i select the userhost from dba_audit_session it gave me the application server name , is there any way to return the real hostname of client side , by the way i configured the WebUtil if it useful to solve this problem.
best regards;
|
|
|
auditing failed login via application server [message #261003 is a reply to message #255443] |
Tue, 21 August 2007 08:56 |
kafaween
Messages: 7 Registered: August 2007 Location: Jordan
|
Junior Member |
|
|
Hi all ;
We have 3-tier architecture in our site (the end users connect to Database 10g via Application Server 10g) ,I need a solution for auditing the failed login attempts, i.e. retrieving information about the end users (hostname , os user), i activate audit_trail='DB' ,
When we make
SQL> select username, userhost, os_username from dba_audit_session;
USERNAME USERHOST OS_USERNAME
------- -------- -----------
scott host01 user01
scott app01 oracle
So as you see , I have the oracle owner (oracle) and the application server name (app01) when I logged from oracle application server,
where as it is clear to see all information when you log direct to Database such as SQL*PLUS(userhost = host01, OS_USER=user01).
by the way we configure WebUtil on the application server .
How we can take the advantage of webutil to audit the failed login through oracle application server either by using audit trail or Logon triggers.
Best regards;
|
|
|
|
|
|
|
|
|