Date:         Tue, 3 Feb 2004 14:38:02 -0600
Reply-To:     "Skinner, Deborah" <Deborah.Skinner@US.FORTIS.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "Skinner, Deborah" <Deborah.Skinner@US.FORTIS.COM>
Subject:      SAS access to Oracle tables - method to avoid having id's and
              passwords embedded in code???
Content-Type: text/plain; charset="us-ascii"

We are implementing SAS 8.2 in a Windows Server environment and have
licensed the SAS/Access to Oracle product.  The vast majority of our SAS
code will be accessing this Oracle data.  
 
But the first major bump in the road is that our DBA's and IT admins are
very concerned about having the Oracle ID's and passwords embedded all
over the place in SAS code.   The first issue is the obvious security
issue.  The second is that ultimately many of these programs will be run
by a scheduler and once code is automated, nobody wants to have to go
back in and maintain the passwords.  
 
I am certain that this must be a common problem and I'm wondering how
other sites have approached this.  
 
 

****************************************************************
	             Please Note
The information in this E-mail message is legally privileged
and confidential information intended only for the use of the
individual(s) named above. If you, the reader of this message,
are not the intended recipient, you are hereby notified that 
you should not further disseminate, distribute, or forward this
E-mail message. If you have received this E-mail in error,
please notify the sender. Thank you
*****************************************************************