RE: Restrict login for a particular user to be only from particul ar m achines

From: <JApplewhite_at_austinisd.org>
Date: Wed, 13 Sep 2006 13:39:26 -0500
Message-ID: <OFBE2F0632.BAA2F3D5-ON862571E8.0066533F-862571E8.006683C2@austinisd.org>

Paul,

To prevent logon, shouldn't this be a Before Logon trigger?

Jack C. Applewhite - Database Administrator Austin (Texas) Independent School District 512.414.9715 (wk) / 512.935.5929 (pager)

 I feel so unnecessary. -- Rufus Thomas

               ( "Do the Funky Chicken")

"Baumgartel, Paul" <paul.baumgartel_at_credit-suisse.com> Sent by: oracle-l-bounce_at_freelists.org
09/13/2006 01:24 PM
Please respond to
paul.baumgartel_at_credit-suisse.com

To
"'Bobak, Mark'" <Mark.Bobak_at_il.proquest.com>, salem.ghassan_at_gmail.com cc
oracle-l_at_freelists.org
Subject
RE: Restrict login for a particular user to be only from particul ar m achines

Thanks for all the replies. My initial attempts used an AFTER LOGON ON SCHEMA, not DATABASE, trigger.  

However, I'm now stymied in a simple test case: the following SYS trigger is firing, but no error appears on login.  

create or replace trigger verify_client
after logon on database when (user='PB') begin

    insert into pb.foo values('Test');
    commit;
    raise_application_error(-20999,'Not authorized'); end;
/
Here's what happens:  

SQL> @conn pb/pb
Connected.
PB_at_CSAR.REGRESS.COM> select * from foo;  

BAR

---

Test  

PB_at_CSAR.REGRESS.COM> @conn pb/pb
Connected.
PB_at_CSAR.REGRESS.COM> select * from foo;  

BAR

---

Test
Test  

As you can probably guess, I added the "insert into pb.foo" to the trigger to verify that it is firing.
What's wrong here?  

Thanks  

Paul Baumgartel
CREDIT SUISSE
Information Technology
DBA & Admin - NY, KIGA 1
11 Madison Avenue
New York, NY 10010
USA
Phone 212.538.1143
paul.baumgartel_at_credit-suisse.com
www.credit-suisse.com

--
http://www.freelists.org/webpage/oracle-l

Received on Wed Sep 13 2006 - 13:39:26 CDT