4
Configuring RADIUS Authentication

This chapter describes how to configure Oracle Advanced Security for the Oracle9i server, for use with RADIUS (Remote Authentication Dial-In User Service). This chapter contains the following topics:

• RADIUS Overview
• RADIUS Authentication Modes
• Enabling RADIUS Authentication, Authorization, and Accounting
• Using RADIUS to Log In to a Database
• RSA ACE/Server Configuration Checklist

RADIUS Overview

RADIUS is a client/server security protocol widely used to enable remote authentication and access. Oracle Advanced Security uses this industry standard in a client/server network environment.

You can enable the network to use any authentication method that supports the RADIUS standard, including token cards and smart cards, by installing and configuring the RADIUS protocol. Moreover, when you use RADIUS, you can change the authentication method without modifying either the Oracle client or the Oracle database server.

From the user's perspective, the entire authentication process is transparent. When the user seeks access to an Oracle database server, the Oracle database server, acting as the RADIUS client, notifies the RADIUS server. The RADIUS server:

• Looks up the user's security information.
• Passes authentication and authorization information between the appropriate authentication server or servers and the Oracle database server.
• Grants the user access to the Oracle database server.
• Logs session information, including when, how often, and for how long the user was connected to the Oracle database server.

The Oracle/RADIUS environment is displayed in Figure 4-1:

Figure 4-1 RADIUS in an Oracle Environment

Text description of the illustration asoag003.gif

The Oracle database server acts as the RADIUS client, passing information between the Oracle client and the RADIUS server. Similarly, the RADIUS server passes information between the Oracle database server and the appropriate authentication servers. The authentication components are listed in Table 4-1:

Table 4-1 RADIUS Authentication Components

Component	Stored Information
Oracle client	Configuration setting for communicating through RADIUS.
Oracle database server/ RADIUS client	Configuration settings for passing information between the Oracle client and the RADIUS server. The secret key file.
RADIUS server	Authentication and authorization information for all users. Each client's name or IP address. Each client's shared secret. Unlimited number of menu files enabling users already authenticated to select different login options without reconnecting.
Authentication server or servers	User authentication information such as passcodes and PINs, depending on the authentication method in use. Note: The RADIUS server can also be the authentication server.

A RADIUS server vendor is often the authentication server vendor as well, in which case authentication can be processed on the RADIUS server. For example, the RSA ACE/Server is both a RADIUS server and an authentication server. It thus authenticates the user's passcode.

RADIUS Authentication Modes

User authentication can take place in either of two ways:

• Synchronous Authentication Mode
• Challenge-Response (Asynchronous) Authentication Mode

Synchronous Authentication Mode

In the synchronous mode, RADIUS lets you use various authentication methods, including passwords and SecurID token cards. Figure 4-2 shows the sequence in which synchronous authentication occurs:

Figure 4-2 Synchronous Authentication Sequence

Text description of the illustration ano81010.gif

1. A user logs in by entering a connect string, passcode, or other value. The client system passes this data to the Oracle database server.
2. The Oracle database server, acting as the RADIUS client, passes the data from the Oracle client to the RADIUS server.
3. The RADIUS server passes the data to the appropriate authentication server, such as Smart Card or SecurID ACE for validation.
4. The authentication server sends either an Access Accept or an Access Reject message back to the RADIUS server.
5. The RADIUS server passes this response to the Oracle database server / RADIUS client.
6. The Oracle database server / RADIUS client passes the response back to the Oracle client.

Example: Synchronous Authentication with SecurID Token Cards

With SecurID authentication, each user has a token card that displays a dynamic number that changes every sixty seconds. To gain access to the Oracle database server/RADIUS client, the user enters a valid passcode that includes both a personal identification number (PIN) and the dynamic number currently displayed on the user's SecurID card. The Oracle database server passes this authentication information from the Oracle client to the RADIUS server, which in this case is the authentication server for validation. Once the authentication server (RSA ACE/Server) validates the user, it sends an "accept" packet to the Oracle database server, which, in turn, passes it to the Oracle client. The user is now authenticated and able to access the appropriate tables and applications.

Challenge-Response (Asynchronous) Authentication Mode

When the system uses the asynchronous mode, the user does not need to enter a user name and password at the SQL*Plus CONNECT string. Instead, a graphical user interface asks the user for this information later in the process.

Figure 4-3 shows the sequence in which challenge-response (asynchronous) authentication occurs.

Figure 4-3 Asynchronous Authentication Sequence

Text description of the illustration ano81011.gif

1. A user seeks a connection to an Oracle database server. The client system passes the data to the Oracle database server.
2. The Oracle database server, acting as the RADIUS client, passes the data from the Oracle client to the RADIUS server.
3. The RADIUS server passes the data to the appropriate authentication server, such as a Smart Card, SecurID ACE, or token card server.
4. The authentication server sends a challenge, such as a random number, to the RADIUS server.
5. The RADIUS server passes the challenge to the Oracle database server / RADIUS client.
6. The Oracle database server / RADIUS client, in turn, passes it to the Oracle client. A graphical user interface presents the challenge to the user.
7. The user provides a response to the challenge. To formulate a response, the user can, for example, enter the received challenge into the token card. The token card provides a dynamic password to be entered into the graphical user interface. The Oracle client passes the user's response to the Oracle database server / RADIUS client.
8. The Oracle database server / RADIUS client sends the user's response to the RADIUS server.
9. The RADIUS server passes the user's response to the appropriate authentication server for validation.
10. The authentication server sends either an Access Accept or an Access Reject message back to the RADIUS server.
11. The RADIUS server passes the response to the Oracle database server / RADIUS client.
12. The Oracle database server / RADIUS client passes the response to the Oracle client.

Example: Asynchronous Authentication with Smart Cards

With smart card authentication, the user logs in by inserting the smart card--a plastic card (like a credit card) with an embedded integrated circuit for storing information--into a hardware device which reads the card. The Oracle client sends the login information contained in the smart card to the authentication server by way of the Oracle database server/RADIUS client and the RADIUS server. The authentication server sends back a challenge to the Oracle client, by way of the RADIUS server and the Oracle database server, prompting the user for authentication information. The information could be, for example, a PIN as well as additional authentication information contained on the smart card.

The Oracle client sends the user's response to the authentication server by way of the Oracle database server and the RADIUS server. If the user has entered a valid number, the authentication server sends an "accept" packet back to the Oracle client by way of the RADIUS server and the Oracle database server. The user is now authenticated and authorized to access the appropriate tables and applications. If the user has entered incorrect information, the authentication server sends back a message rejecting the user's access.

Example: Asynchronous Authentication with ActivCard Tokens

One particular ActivCard token is a hand-held device with a keypad and which displays a dynamic password. When the user seeks access to an Oracle database server by entering a password, the information is passed to the appropriate authentication server by way of the Oracle database server/RADIUS client and the RADIUS server. The authentication server sends back a challenge to the client--by way of the RADIUS server and the Oracle database server. The user types that challenge into the token, and the token displays a number for the user to send in response.

The Oracle client then sends the user's response to the authentication server by way of the Oracle database server and the RADIUS server. If the user has typed a valid number, the authentication server sends an "accept" packet back to the Oracle client by way of the RADIUS server and the Oracle database server. The user is now authenticated and authorized to access the appropriate tables and applications. If the user has entered an incorrect response, the authentication server sends back a message rejecting the user's access.

Enabling RADIUS Authentication, Authorization, and Accounting

To enable RADIUS authentication and accounting, perform the following tasks:

• Task 1: Install RADIUS on the Oracle Database Server and on the Oracle Client
• Task 2: Configure RADIUS Authentication
• Task 3: Create a User and Grant Access
• Task 4: Configure External RADIUS Authorization (optional)
• Task 5: Configure RADIUS Accounting
• Task 6: Add the RADIUS Client Name to the RADIUS Server Database
• Task 7: Configure the Authentication Server for Use with RADIUS.
• Task 8: Configure the RADIUS Server for Use with the Authentication Server
• Task 9: Configure Mapping Roles

Task 1: Install RADIUS on the Oracle Database Server and on the Oracle Client

RADIUS is installed with Oracle Advanced Security during a typical installation of Oracle9i.

Task 2: Configure RADIUS Authentication

This task includes the following steps:

• Step 1: Configure RADIUS on the Oracle Client
• Step 2: Configure RADIUS on the Oracle Database Server
• Step 3: Configure Additional RADIUS Features

Unless otherwise indicated, perform these configuration tasks by using Oracle Net Manager or by using any text editor to modify the sqlnet.ora file.

Step 1: Configure RADIUS on the Oracle Client

1. To start Oracle Net Manager:
   • On UNIX, run netmgr from $ORACLE_HOME/bin.
   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Oracle Net Manager.
2. In the Navigator window, expand Local > Profile.
3. From the list in the right pane, select Oracle Advanced Security; the Oracle Advanced Security tabbed window appears (Figure 4-4):

Figure 4-4 Oracle Advanced Security Authentication Window

Text description of the illustration radu0001.gif

• Choose the Authentication tab.
• From the Available Methods list, select RADIUS.
• Choose the right-arrow [>] to move RADIUS to the Selected Methods list. Move any other methods you want to use in the same way.
• Arrange the selected methods in order of required usage by selecting a method in the Selected Methods list, and clicking Promote or Demote to position it in the list. For example, put RADIUS at the top of the list for it to be the first service used.
• Choose File > Save Network Configuration.

  The sqlnet.ora file is updated with the following entry:

  SQLNET.AUTHENTICATION_SERVICES=(RADIUS)

  Step 2: Configure RADIUS on the Oracle Database Server

  • Create the RADIUS Secret Key File on the Oracle Database Server
  • Configure RADIUS Parameters on the Server (sqlnet.ora file)
  • Set Oracle Database Server Initialization Parameters

  Create the RADIUS Secret Key File on the Oracle Database Server

  1. Obtain the RADIUS secret key from the RADIUS server. For each RADIUS client, the administrator of the RADIUS server creates a shared secret key, which must be longer than 16-characters.
  2. On the Oracle database server, create a directory $ORACLE_HOME/network/security on UNIX or ORACLE_HOME\network\security on Windows NT.
  3. Create the file radius.key to hold the shared secret copied from the RADIUS server. Place the file in the directory you just created in Step 2.
  4. Copy the shared secret key and paste it (and nothing else) into the radius.key file created on the Oracle database server.
  5. For security purposes, change the file permission of radius.key to read only, accessible only by the Oracle owner (Oracle relies on the file system to keep this file secret).

     See Also: The RADIUS server administration documentation, for information about obtaining the secret key

  Configure RADIUS Parameters on the Server (sqlnet.ora file)

  1. Start Oracle Net Manager:
     • On UNIX, run netmgr from $ORACLE_HOME/bin.
     • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Oracle Net Manager.
  2. In the Navigator window, expand Local > Profile.
  3. From the list in the right pane, select Oracle Advanced Security; the Oracle Advanced Security tabbed window appears (Figure 4-4).
  4. Choose the Authentication tab.
  5. From the Available Methods list, select RADIUS.
  6. Move RADIUS to the Selected Methods list by choosing the right-arrow [>].
  7. To arrange the selected methods in order of desired use, select a method in the Selected Methods list, and choose Promote or Demote to position it in the list. For example, if you want RADIUS to be the first service used, put it at the top of the list.
  8. Choose the Other Params tab; the Other Params window appears (Figure 4-5):

  Figure 4-5 Oracle Advanced Security Other Params Window

  

  Text description of the illustration radu0002.gif

• From the Authentication Service list, select RADIUS.
• In the Host Name field, accept the localhost as the default primary RADIUS server, or enter another host name.
• Ensure that the default value of the Secret File field is valid.
• Choose File > Save Network Configuration.

  The sqlnet.ora file is updated with the following entries:

  SQLNET.AUTHENTICATION_SERVICES=RADIUS

  SQLNET.RADIUS_AUTHENTICATION=RADIUS_server_{hostname|IP_address}

  Set Oracle Database Server Initialization Parameters

  Configure the initialization parameter file, located in

  • On Unix, $ORACLE_BASE\admin\db_name\pfile
  • On Windows NT, ORACLE_BASE/admin/db_name/pfile

  with the following values:

  REMOTE_OS_AUTHENT=FALSE
  OS_AUTHENT_PREFIX=""
  
  

  Caution: Setting REMOTE_OS_AUTHENT to TRUE can enable a security breach because it lets someone using a non-secure protocol, such as TCP, perform an operating system-authorized login (formerly called an OPS$ login).

  See Also: Oracle9i Database Reference and the Oracle9i Database Administrator's Guide, for information about setting initialization parameters on the Oracle9i database server

  Step 3: Configure Additional RADIUS Features

  • Change Default Settings
  • Configure Challenge-Response
  • Set Parameters for an Alternate RADIUS Server

  Change Default Settings

  1. To start Oracle Net Manager:
     • On UNIX, run netmgr from $ORACLE_HOME/bin.
     • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Oracle Net Manager.
  2. In the Navigator window, expand Local > Profile.
  3. From the list in the right window pane, select Oracle Advanced Security; the Oracle Advanced Security tabbed window appears (Figure 4-5).
  4. Choose the Other Params tab.
  5. From the Authentication Service list, select RADIUS.
  6. Change the default setting for any of the following fields:

     Field	Description
     Port Number	Specifies the listening port of the primary RADIUS server. The default value is 1645.
     Timeout (seconds)	Specifies the time the Oracle database server waits for a response from the primary RADIUS server. The default is 15 seconds.
     Number of Retries	Specifies the number of times the Oracle database server resends messages to the primary RADIUS server. The default is three retries. For instructions on configuring RADIUS accounting, see: Task 5: Configure RADIUS Accounting.
     Secret File	Specifies the location of the secret key on the Oracle database server. The field specifies the location of the secret key file, not the secret key itself. For information about specifying the secret key, see: Create the RADIUS Secret Key File on the Oracle Database Server.

  7. Choose File > Save Network Configuration.

     The sqlnet.ora file is updated with the following entries:

     SQLNET.RADIUS_AUTHENTICATION_PORT=(PORT)
     SQLNET.RADIUS_AUTHENTICATION_TIMEOUT=
     
     (NUMBER OF SECONDS TO WAIT FOR response)
     SQLNET.RADIUS_AUTHENTICATION_RETRIES=
     
     (NUMBER OF TIMES TO RE-SEND TO RADIUS server)
     SQLNET.RADIUS_SECRET=(path/radius.key)
     
     

  Configure Challenge-Response

  The challenge-response (asynchronous) mode presents the user with a graphical interface requesting first a password, then additional information--for example, a dynamic password that the user obtains from a token card. With the RADIUS adapter, this interface is Java-based to provide optimal platform independence.

  Note: Third party vendors of authentication devices must customize this graphical user interface to fit their particular device. For example, a smart card vendor would customize the Java interface so that the Oracle client reads data, such as a dynamic password, from the smart card. When the smart card receives a challenge, it responds by prompting the user for more information, such as a PIN.

  See Also: Appendix C, Integrating Authentication Devices Using RADIUS, for information about how to customize the challenge-response user interface

  To configure challenge-response:

  1. If you are using JDK 1.1.7 or JRE 1.1.7, set the JAVA_HOME environment variable to the JRE or JDK location on the system where the Oracle client is run:
     • On UNIX, enter this command at the prompt:

       % setenv JAVA_HOME /usr/local/packages/jre1.1.7B
       
       

     • On Windows NT, choose Start> Settings > Control Panel > System > Environment, and set the JAVA_HOME variable as follows:

       c:\java\jre1.1.7B
       
       

       Note: This step is not required for any other JDK / JRE version.

  2. Start Oracle Net Manager:
     • On UNIX, run netmgr from $ORACLE_HOME/bin.
     • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Oracle Net Manager.
  3. In the Navigator window, expand Local > Profile.
  4. From the list in the right pane, select Oracle Advanced Security; the Oracle Advanced Security Other Params window appears (Figure 4-5).
  5. Choose the Other Params tab.
  6. From the Authentication Service list, select RADIUS.
  7. In the Challenge Response field, enter ON to enable challenge-response.
  8. In the Default Keyword field, accept the default value of the challenge or enter a keyword for requesting a challenge from the RADIUS server.

     Note: The keyword feature is provided by Oracle and supported by some, but not all, RADIUS servers. You can use this feature only if your RADIUS server supports it. By setting a keyword, you let the user avoid using a password to verify identity. If the user does not enter a password, the keyword you set here is passed to the RADIUS server which responds with a challenge requesting, for example, a driver's license number or birth date. If the user does enter a password, the RADIUS server may or may not respond with a challenge, depending upon the configuration of the RADIUS server.

  9. In the Interface Class Name field, accept the default value of DefaultRadiusInterface or enter the name of the class you have created to handle the challenge-response conversation. If other than the default RADIUS interface is used, you also must edit the sqlnet.ora file to enter SQLNET.RADIUS_CLASSPATH=(location), where location is the complete path name of the jar file. It defaults to
     $ORACLE_HOME/network/jlib/netradius.jar: $oracle_home/JRE/lib/vt.jar
  10. Choose File > Save Network Configuration.

      The sqlnet.ora file is updated with the following entries:

      SQLNET.RADIUS_CHALLENGE_RESPONSE=([ON | OFF])
      SQLNET.RADIUS_CHALLENGE_KEYWORD=(KEYWORD)
      SQLNET.RADIUS_AUTHENTICATION_INTERFACE=(name of interface including the 
      package name delimited by "/" for ".")
      

  Set Parameters for an Alternate RADIUS Server

  If you are using an alternate RADIUS server, set these parameters in the sqlnet.ora file using any text editor.

  SQLNET.RADIUS_ALTERNATE=(hostname or ip address of alternate radius server)
  SQLNET.RADIUS_ALTERNATE_PORT=(1812)
  SQLNET.RADIUS_ALTERNATE_TIMEOUT=(number of seconds to wait for response)
  SQLNET.RADIUS_ALTERNATE_RETRIES=(number of times to re-send to radius server)
  
  

  Task 3: Create a User and Grant Access

  To grant user access:

  1. Launch SQL*Plus and execute these commands to create and grant access to a user identified externally on the Oracle database server.

     SQL> CONNECT system/manager@database_name;
     SQL> CREATE USER username IDENTIFIED EXTERNALLY;
     SQL> GRANT CREATE SESSION TO USER username;
     SQL> EXIT
     
     
     

     If you are using Windows NT, you can use the Security Manager tool in the Oracle Enterprise Manager.

     See Also: Oracle9i Database Administrator's Guide Oracle9i Heterogeneous Connectivity Administrator's Guide

  2. Enter the same user in the RADIUS server's users file.

     See Also: Administration documentation for the RADIUS server

  Task 4: Configure External RADIUS Authorization (optional)

  If you require external RADIUS authorization for RADIUS users who connect to an Oracle database, then you must perform the following steps to configure the Oracle server, the Oracle client, and the RADIUS server:

  To configure the Oracle server (RADIUS client):

  1. Add the OS_ROLE parameter to the init.ora file and set this parameter to TRUE as follows:

     OS_ROLE=TRUE
     
     

     Then restart the database so the system can read the change to the init.ora file.

  2. Set the RADIUS challenge-response mode to ON for the server if you have not already done so by following the steps listed in "Configure Challenge-Response".
  3. Add externally identified users and roles.

  To configure the Oracle client (where users log in):

  Set the RADIUS challenge-response mode to ON for the client if you have not already done so by following the steps listed in "Configure Challenge-Response".

  To configure the RADIUS server:

  1. Add the following attributes to the RADIUS server attribute configuration file:

     ATTRIBUTE NAME	CODE	TYPE
     VENDOR_SPECIFIC	26	Integer
     ORACLE_ROLE	1	String

  2. Assign a Vendor ID for Oracle in the RADIUS server attribute configuration file that includes the SMI Network Management Private Enterprise Code of 111.

     For example, enter the following in the RADIUS server attribute configuration file:

     VALUE     VENDOR_SPECIFIC     ORACLE     111
     
     

  3. Using the following syntax, add the ORACLE_ROLE attribute to the user profile of the users who will use external RADIUS authorization:

     ORA_databaseSID_rolename[_[A]|[D]]
     
     

     where:

     • ORA designates that this role is used for Oracle purposes
     • databaseSID is the Oracle system identifier that is configured in the database server's init.ora file
     • rolename is the name of role as it is defined in the data dictionary. For example, SYSDBA
     • A is an optional character that indicates the user has adminstrator's privileges for this role
     • D is an optional character that indicates this role is to be enabled by default

     Ensure that RADIUS groups which map to Oracle roles adhere to the ORACLE_ROLE syntax.

     For example:

     USERNAME     USERPASSWD="user_password",
                  SERVICE_TYPE=login_user,
                  VENDOR_SPECIFIC=ORACLE,
                  ORACLE_ROLE=ORA_ora920_sysdba
     

     See Also: The RADIUS server administration documentation for information about configuring the server.

  Task 5: Configure RADIUS Accounting

  RADIUS accounting logs information about access to the Oracle database server and stores it in a file on the RADIUS accounting server. Use this feature only if both the RADIUS server and authentication server support it.

  Set RADIUS Accounting on the Oracle Database Server

  To enable or disable RADIUS accounting:

  1. Start Oracle Net Manager:
     • On UNIX, run netmgr from $ORACLE_HOME/bin.
     • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Oracle Net Manager.
  2. In the Navigator window, expand Local > Profile.
  3. From the list in the right window pane, select Oracle Advanced Security; the Oracle Advanced Security Other Params window appears (Figure 4-5).
  4. Choose the Other Params tab.
  5. From the Authentication Service list, select RADIUS.
  6. In the Send Accounting field, enter ON to enable accounting or OFF to disable accounting.
  7. Choose File > Save Network Configuration.

     The sqlnet.ora file is updated with the following entry:

     SQLNET.RADIUS_SEND_ACCOUNTING= ON

  Configure the RADIUS Accounting Server

  RADIUS Accounting consists of an accounting server residing on either the same host as the RADIUS authentication server or on a separate host.

  See Also: Administration documentation for the RADIUS server, for information about configuring RADIUS accounting

  Task 6: Add the RADIUS Client Name to the RADIUS Server Database

  You can use virtually any RADIUS server that complies with the standards in the Internet Engineering Task Force (IETF) RFC #2138, Remote Authentication Dial In User Service (RADIUS) and RFC #2139 RADIUS Accounting. Because RADIUS servers vary, consult the documentation for your particular RADIUS server for any unique interoperability requirements.

  Perform the following steps to add the RADIUS client name to a Livingston RADIUS server:

  1. Open the clients file, which can be found at /etc/raddb/clients. The following text and table appear:

     @ (#) clients 1.1 2/21/96 Copyright 1991 Livingston Enterprises Inc
     This file contains a list of clients which are allowed to make 
     authentication requests and their encryption key. The first field is a valid 
     hostname. The second field (separated by blanks or tabs) is the encryption 
     key.
     Client Name                     Key
     
     
     

  2. In the CLIENT NAME column, enter the host name or IP address of the host on which the Oracle database server is running. In the KEY column, type the shared secret.

     The value you enter in the CLIENT NAME column, whether it is the client's name or IP address, depends on the RADIUS server.

  3. Save and close the clients file.

     See Also: Administration documentation for the RADIUS server

  Task 7: Configure the Authentication Server for Use with RADIUS

  See the authentication server documentation for instructions about configuring the authentication servers.

  See Also: "Related Documentation", which contains a list of possible resources.

  Task 8: Configure the RADIUS Server for Use with the Authentication Server

  See the RADIUS server documentation.

  Task 9: Configure Mapping Roles

  If the RADIUS server supports vendor type attributes, you can manage roles by storing them in the RADIUS server. The Oracle database server downloads the roles when there is a CONNECT request using RADIUS.

  To use this feature, configure roles on both the Oracle database server and the RADIUS server.

  Perform these steps to configure roles on the Oracle database server:

  1. Use a text editor to set the OS_ROLES parameter in the initialization parameters file on the Oracle database server.
  2. Stop and restart the Oracle database server.
  3. Create each role the RADIUS server is to manage on the Oracle database server with IDENTIFIED EXTERNALLY.

     To configure roles on the RADIUS server, refer to Table 4-1 and use the following syntax:

     ORA_DatabaseName.DatabaseDomainName_RoleName

     Example:

     ORA_USERDB.US.ORACLE.COM_MANAGER

     RADIUS Configuration Parameters

     Parameter	Description
     DatabaseName	The name of the Oracle database server for which the role is being created. This is the same as the value of the DB_NAME initialization parameter.
     DatabaseDomainName	The name of the domain to which the Oracle database server belongs. The value is the same as the value of the DB_DOMAIN initialization parameter.
     RoleName	The name of the role created in the Oracle database server.

  4. Configure RADIUS challenge-response mode.

     To configure challenge-response mode, See:

     • Challenge-Response (Asynchronous) Authentication Mode
     • Configure Challenge-Response

  Using RADIUS to Log In to a Database

  If you are using the synchronous authentication mode, launch SQL*Plus and enter the following command at the prompt:

  CONNECT username/password@database_alias
  
  

  Note that you can log in with this command only when challenge-response is not turned to ON.

  If you are using the challenge-response mode, launch SQL*Plus and, at the prompt, enter the command that follows:

  CONNECT /@database_alias
  
  

  Note that you can log in with this command only when challenge-response is turned to ON.

  Note: The challenge-response mode can be configured for all login cases.

  RSA ACE/Server Configuration Checklist

  If you are using an RSA ACE/Server as a RADIUS server, check the following items before making your initial connection:

  • Ensure that the host agent in the RSA ACE/Server is set up to send a node secret. In version 5.0, this is done by leaving the SENT Node secret box unchecked. If the RSA ACE/Server fails to send a node secret to the agent, then a node verification failure message will be written to the RSA ACE/Server log.
  • If you are using RSA SecurID tokens, then ensure that the token is synchronized with the RSA ACE/Server.

    See Also: RSA ACE/Server documentation for specific information about troubleshooting.