作業系統認證與ORACLE密碼檔案認證方式

Operating system (OS) authentication and Password files authentication

所討論的是關於具有SYSDBA or SYSOPER的特權使用者的認證方式

 

目錄

1 overview of authentication for adminnistrator

2 Password file authentication method

3 OS authentication method

4 Preparing to Use OS Authentication

5 Preparing to Use Password File Authentication

6 OSDBA and OSOPER相關

 

1 overview of authentication for adminnistrator

 

To connect to Oracle as a privileged user over a local connection or a secure remote connection, you have the following options:

l         You can connect and be authenticated by a password file; provided the database has a password file and you have been granted the SYSDBA or SYSOPER system privilege.

 

l         If the server is not using a password file, or if you have not been granted SYSDBA or SYSOPER privileges and are therefore not in the password file, you can use OS authentication. On most operating systems, OS authentication for database dministrators involves placing the OS username of the database administrator in a special group, generically referred to as OSDBA.

(你只能夠在兩種情況下以 privileged user  connect to database.

l         一個database user, have been granted the SYSDBA or SYSOPER system privilege. 透過Password file authenticated method.

 

 

l         在OS xxx 使用者環境下，如果這個使用者 xxx 是 OSDBA (dba) 組中的一員.

 

 

Example: gdut is a normal user

 

2 Password file authentication method.

 

 

Of course, the REMOTE_LOGIN_PASSWORDFILE must be exclusive to use password file authentication.

 

 

 

3 OS authentication method

 

 

 

Your choice will be influenced by whether you intend to administer your database locally on the same machine where the database resides, or whether you intend to administer many different databases from a single remote client.

 

 

4 Preparing to Use OS Authentication

 

To enable authentication of an administrative user using the operating system you must do the following:

1. Create an operating system account for the user.

 

2. Add the user to the OSDBA or OSOPER operating system defined groups.

 

3. Ensure that the initialization parameter, REMOTE_LOGIN_PASSWORDFILE, is set to NONE. This is the default value for this parameter.

 

這是怎麼回事，remote_login_passwordfile 並不是NONE，但仍可用OS authenticated method login ?

兩種方式可以並存

Operating system authentication takes precedence over password file authentication. (因為OS 認證方式優於Password File 認證方式)

Connecting Using OS Authentication

A user can be authenticated, enabled as an administrative user, and connected to a local database by typing one of the following SQL*Plus commands:

 

 

For a remote database connection over a secure connection, the user must also specify the net service name of the remote database:

 

 

OS authentication has nothing to do with whether you connect database locally or remotely.

 

 

5 Preparing to Use Password File Authentication

 

To enable authentication of an administrative user using password file authentication you must do the following:

1. Create an operating system account for the user.

 

2. If not already created, create the password file using the ORAPWD utility:

 

 

3. Set the REMOTE_LOGIN_PASSWORDFILE initialization parameter to EXCLUSIVE.

 

4. Connect to the database as user SYS (or as another user with the administrative privilege).

 

5. If the user does not already exist in the database, create the user. Grant the SYSDBA or SYSOPER system privilege to the user:

 

 

This statement adds the user to the password file, thereby enabling connection AS SYSDBA.

 

如果使用者所在的組是OSDBA group (dba), 那麼就可以在這個使用者下 conn / as sysdba ,以作業系統認證方式登入，否則報insufficient privileges.

 

6 OSDBA and OSOPER相關

 

Two special operating system groups control database administrator connections when using OS authentication. These groups are generically referred to as OSDBA and OSOPER.

The following describes how membership in the OSDBA or OSOPER group affects your connection to Oracle:

      If you are a member of the OSDBA group, and specify AS SYSDBA when you connect to the database, you are granted the SYSDBA system privilege.

If you are a member of the OSOPER group, and specify AS SYSOPER when you connect to the database, you are granted the SYSOPER system privilege.

If you are not a member of the associated operating system group for SYSDBA or SYSOPER system privileges, the CONNECT command fails.