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

From: Bobak, Mark <Mark.Bobak_at_il.proquest.com>
Date: Wed, 13 Sep 2006 12:32:16 -0400
Message-ID: <AA29A27627F842409E1D18FB19CDCF2709831802@AABO-EXCHANGE02.bos.il.pqe>

Ghassan beat me to it....

See:
http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:50698 74198829

For a nice example.

-Mark

-- 
Mark J. Bobak 
Senior Oracle Architect 
ProQuest Information & Learning 

"A human being should be able to change a diaper, plan an invasion,
butcher a hog, conn a ship, design a building, write a sonnet, balance
accounts, build a wall, set a bone, comfort the dying, take orders, give
orders, cooperate, act alone, solve equations, analyze a new problem,
pitch manure, program a computer, cook a tasty meal, fight efficiently,
die gallantly. Specialization is for insects."   --Robert A. Heinlein


 

________________________________

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Ghassan Salem
Sent: Wednesday, September 13, 2006 12:31 PM
To: Baumgartel, Paul
Cc: oracle-l_at_freelists.org
Subject: Re: Restrict login for a particular user to be only from
particul ar m achines


raise an error (raise_application_error, or simply raise any_error)


On 9/13/06, Baumgartel, Paul < paul.baumgartel_at_credit-suisse.com


<mailto:paul.baumgartel_at_credit-suisse.com> > wrote: 


	Right, but if the machine name isn't one of the allowed
machines, what action does the trigger take?  
	
	 

	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: Ghassan Salem [mailto:salem.ghassan_at_gmail.com]
		Sent: Wednesday, September 13, 2006 12:29 PM
		To: paul.baumgartel_at_credit-suisse.com
		Cc: oracle-l_at_freelists.org
		Subject: Re: Restrict login for a particular user to be
only from particular m achines
		
		
		use a logon trigger to test for the machine's name/ip
		rgds
		
		
		On 9/13/06, Baumgartel, Paul


<paul.baumgartel_at_credit-suisse.com > wrote: 


			All,
			 
			A client wants to be able to limit login for
particular database user to be from a specified set of client machines.
My understanding of login restriction at the listener level is that it
is possible only to limit all database logins based on machine.  I've
been experimenting with login triggers that inspect
sys_context('userenv','host'), but haven't figured out how to prevent
the session from proceeding if the client machine name is not in the
approved list.  If anyone has any ideas or suggestions I'd be most
grateful.
			 
			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.credit-suisse.com/legal/en/disclaimer_email_ib.html> 

	
========================================================================
======
			

			


	

	
========================================================================
======
	Please access the attached hyperlink for an important electronic
communications disclaimer: 
	
	
	http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html


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

	
========================================================================
======
	

	



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

Received on Wed Sep 13 2006 - 11:32:16 CDT