Oracle will require you to configure the Oracle RDBMS to use operating system authentication but if you inherit an Oracle instance, you will want to disable os authentication when possible. When the OS_AUTHENT_PREFIX is set, any os user that is created with “IDENTIFIED EXTERNALLY” will have the prefix. For example, in the below example, the value is “ops$”. The os user johnnybgood will have an internal Oracle user id of “ops$johnnybgood”. It’s a handy way to quickly identify such users but it isn’t full proof.
show parameter OS_AUTHENT_PREFIX
lang-NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
os_authent_prefix string ops$
To determine exactly which users are set up for os authentication run the following query:
set pagesize 5000
set linesize 999
set trimspool on
select gn.GLOBAL_NAME as "Instance", username, authentication_type
from dba_users du, global_name gn
where authentication_type = 'EXTERNAL'
Now, there are valid reasons to use os authentication but I would push LDAP long before os authentication.
From the Oracle Security Admin Guide:
Advantages of External Authentication
Following are the advantages of external authentication:
More choices of authentication mechanism are available, such as smart cards, fingerprints, Kerberos, or the operating system.
Many network authentication services, such as Kerberos support single sign-on, enabling users to have fewer passwords to remember.
If you are already using some external mechanism for authentication, such as one of those listed earlier, then there may be less administrative overhead to use that mechanism with the database as well.