Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Restrict login for a particular user to be only from particul ar m achines

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

From: Baumgartel, Paul <paul.baumgartel_at_credit-suisse.com>
Date: Wed, 13 Sep 2006 19:42:23 +0100
Message-ID: <D97D1FAE0521BD44820B920EDAB3BBAC0F40E862@ENYC11P32005.corpny.csfb.com>


Jack,  

Yes, that would do the trick nicely, wouldn't it?  

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

-----Original Message-----

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]On Behalf Of JApplewhite_at_austinisd.org Sent: Wednesday, September 13, 2006 2:39 PM To: oracle-l_at_freelists.org
Subject: RE: Restrict login for a particular user to be only from particul ar m achines

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



Please access the attached hyperlink for an important electronic communications disclaimer:

http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html


--

http://www.freelists.org/webpage/oracle-l Received on Wed Sep 13 2006 - 13:42:23 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US