RE: login auditing

From: Goulet, Richard <Richard.Goulet_at_parexel.com>
Date: Thu, 11 Dec 2008 15:22:18 -0500
Message-ID: <23C4836D8E9C5F4280A66C0C247BC16F20F34DA5@US-BOS-MX011.na.pxl.int>


Use a on logon database trigger. Or use the userhost or terminal columns in sys.aud$.  

Dick Goulet
Senior Oracle DBA
PAREXEL International
978.313.3426
 information transmitted in this communication is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please destroy any copies, contact the sender and delete the material from any computer.  


From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Steiner, Randy Sent: Thursday, December 11, 2008 2:15 PM To: oracle-l_at_freelists.org
Subject: login auditing  

I am currently auditing logins and the audit logs are going directly to a syslog server.

We have an application that maintains its own security and logs into Oracle with an application id (app_user).

Oracle is capturing these logins as for app_user. Is there someway I can use sys_context( 'USERENV' , 'OS_USER' ) to have auditing record the OS user login instead of app_user?  

Thanks

Randy  

--
http://www.freelists.org/webpage/oracle-l
Received on Thu Dec 11 2008 - 14:22:18 CST

Original text of this message