Re: Oracle & UNIX password

From: Kirill Richine <kirill_at_cs.ualberta.ca>
Date: 1996/05/18
Message-ID: <4nl8ln$bq5_at_scapa.cs.ualberta.ca>#1/1


Abdul Sheikh (ab_at_sql2000.demon.co.uk) wrote:
: I guess you are using an ops$ account in the database to overcome
: the password requirement when logged into unix, the only way
: to connect to the data from a client pc is to fully
: issue the ops$username with the password so when you
: setup the user with ...
 

: grant connect,resource to ops$username identified by password.
 

: you would use the password issued in the above statement although
: it will not be required when logging in via unix
 

: regards
: Abdul Sheikh

Sorry, but it does not make any sense!
When you set up an ops$ account in oracle you go

create userid identified externally;
grant connect to userid;

The advantage of this is that DBA does not have to mess with the passowords.

Then, when a user is logged on to the UNIX server, and his unix id is the same as userid (or ops$userid if you are using the default prefix), he can go:

% sqlplus /

But the problem is: how would one do something like this via sqlnet?

Can you explain clearly what exactly one has to do: 1) on the server side
2) on the client (PC) side?

Is it possible to do it without messing with the passwords on oracle side? Is it possible to do it so that the users, on their pc's can use their normal unix passwords when connecting to the database via sqlnet, i.e., something like:

sqlplus userid/unixpasswd_at_t:server:database

Thank you.
k& Received on Sat May 18 1996 - 00:00:00 CEST

Original text of this message