Re: does "identified externally" work?

Thanks to those who offered help regarding "identified externally". It does work. I guess my problem was invoking "sqlplus" and then actually replying with "x" (or "ops$x") when prompted for a username.
(If one replies with a username, you are then prompted for a password.
A null password is not valid at this prompt.) Using "sqlplus /" to bypass both username and password prompts is useful (but not documented?).
(P.S. The default Oracle account associated with os account "x" is "ops$x".
To change this, modify the value of "os_authent_prefix" by placing a line in file configsid.ora. E.g., to make these accounts the same, use "os_authent_prefix = "".)  

Regarding my mention of "default roles", I was referring to the sections in the manuals titled "Using Operating System Role Identification". There are no concrete examples given, but I figured it out. In file configsid.ora, place the line "os_roles = true" (this gives role authorization to the operating system). To give user "x" the "connect" role when starting an oracle session, place the line "ora_sid_connect_d::111:x" in file /etc/group. (I used an unassigned groupid.) This works. While interesting, I can't see giving anyone the privilege of modifying /etc/group for the purpose of administering roles. I don't think I will be using this. (Can anyone give a good reason for doing this instead of using Oracle to grant roles?)  

(P.S. The above refers to Oracle 7.2.3 running on Solaris 2.3.)
Received on Thu Mar 14 1996 - 00:00:00 CET