From MGogala@oxhp.com Thu, 19 Jun 2003 12:41:45 -0700 From: "Gogala, Mladen" Date: Thu, 19 Jun 2003 12:41:45 -0700 Subject: RE: oracle authentication from windows Message-ID: MIME-Version: 1.0 Content-Type: text/plain That, of course, will render your database totally insecure and open to anybody who can bring in a WinXP laptop, change the windoze username and log in as he pleases. DBA that sets his production parameters the way Arup described deserves to be publicly tortured by Bill O'Reilly in the "no spin zone".   Mladen Gogala Oracle DBA Phone:(203) 459-6855 Email:[EMAIL PROTECTED] -----Original Message-----From: Arup Nanda [mailto:[EMAIL PROTECTED]Sent: Thursday, June 19, 2003 3:46 PMTo: Multiple recipients of list ORACLE-LSubject: Re: oracle authentication from windows Sure.   Just declare these in your init.ora   os_authent_prefix=OPS$remote_os_authent=TRUE   bounce the database, add a user called OPS$, e.g. OPS$AK if your Windows login id is AK as   create user ops$ak identified externally   From windows connect as "/@servicename", e.g. sqlplus /@service1   If it doesn't work, the OS user may be different. Use this query while connected to the database from Windows cleint.   SQL> select sys_context('USERENV','OS_USER') from dual;   See what OS username comes up; use that instead.   HTH.   Arup Nanda www.proligence.com    
----- Original Message -----