Oracle Network Products Getting Started for Windows Platforms

Library

Product

Contents

Index

Using the Advanced Networking Option

Setting Up Network Security and Single Sign-On for Windows NT and Windows 95
Setting Up for Network Security and Single Sign-On for Windows 3.1x
Using the NDS Native Naming Adapter

Note The DCE Integration component of ANO requires no platform-specific configuration steps. All ANO features are discussed in the Oracle Advanced Networking Option Administrator's Guide.

Setting Up Network Security and Single Sign-On for
Windows NT and Windows 95

This section describes specific platform-specific configuration steps to perform for Network Security and Single Sign-On on the Windows NT or Windows 95 operating systems.

Additional Information General configuration instructions that you should perform are described in detail in the Oracle Advanced Networking Option Administrator's Guide.

Configuring the Kerberos Authentication Adapter

To use the Kerberos Authentication Adapter on Oracle7 Server for Windows NT operating system, you need to have the root drive :\TMP subdirectory present.

Note You may experience difficulty executing SQL scripts from SQL*Plus if you use the Kerberos Authentication Adapter. Re-installing SQL*Plus for Windows NT and Windows 95 release 3.3.2.0.0 solves this problem.

Configuring the SecurID Authentication Adapter

If you use the SecurID Authentication Adapter on Oracle7 Server for Windows NT, you need the following from your SecurID administrator:

SDCONF.REC file present in the root drive :\TMP
port numbers and service names present in the Windows NT services file

Configuring the CyberSAFE Authentication Adapter

Before using the CyberSAFE Authentication Adapter, you must:

install the CyberSAFE Application Security Toolkit
run the CyberSAFE Challenger Client to get your ticket-granting ticket

Additional Information See the CyberSAFE Application Security Toolkit documentation.

Setting Up for Network Security and Single Sign-On for Windows 3.1x

This section describes specific platform-specific configuration steps to perform for Network Security and Single Sign-On on the Windows 3.1x operating systems.

Additional Information General configuration instructions that you should perform are described in detail in the Oracle Advanced Networking Option Administrator's Guide.

Configuring the CyberSAFE Authentication Adapter

Before using the CyberSAFE Authentication Adapter, you must:

install the CyberSAFE Application Security Toolkit
run the CyberSAFE Challenger Client to get your ticket-granting ticket
have the two configuration files in the directory specified by the CSFC5CONFIG and CSFC5REALMS parameters in AUTOEXEC.BAT
For example:
SET CSFC5CONFIG=C:\CSFC5\KRB.CNF
SET CSFC5REALMS=C:\CSFC5\KRB.REA

Additional Information: To configure SQL*Net for use with the CyberSAFE Adapter, refer to the CyberSAFE Application Security Toolkit documentation and the Oracle Advanced Networking Option Administrator's Guide for detailed information.

Configuring the Kerberos Authentication Adapter

Before using the Kerberos Authentication Adapter, you must

have the two Kerberos configuration files, *.CNF and *.REA, in the directory specified by the SQLNET.KERBEROS5_CONF and SQLNET.KERBEROS5_REALMS parameters in SQLNET.ORA
For example:
SQLNET.KERBEROS5_CONF=C:\ORAWIN\NETWORK\ADMIN\KRB.CNF

Attention You must specify the drive. In this example, the drive is C:\.
run the Oracle Kerberos Utility to obtain a ticket-granting ticket

Using the Oracle Kerberos Utility

The Oracle Kerberos Utility (OKU) allows you to obtain and cache Kerberos tickets. After double-clicking the OKU icon in the Oracle Program Group window, the OKU dialog box appears.

To complete configuration for Windows 3.1x:

Login and Get Ticket.
If you do not have a valid ticket-granting ticket, request one by providing your user name and password to log in to a Kerberos server. You can change the default attributes of the ticket by clicking the Options button.
Select your Options.
Choose OK to save changes.
Choose Browse to select the cache file you want to use.
You can view the ticket information by clicking Show. To remove the cache file, click Remove.
You can leave the OKU by clicking Cancel/Close at any time.

Configuring the SecurID Authentication Adapter

You need the following information from your SecurID administrator if you use the SecurID Authentication Adapter on Oracle7 Server for Windows NT:

SCCONF.REC file present in the root directory drive :\TMP
port numbers and service names present in NT services file

Note The SecurID Authentication Adapter does not support database roles and database links.

Using the NDS Native Naming Adapter

Note The NDS Native Naming Adapter is shipped as a part of SQL*Net. To use the NDS Authentication Adapter, you must run NetWare 4.1 or above with NDS.

The NDS Native Naming Adapter for Windows and Windows NT clients uses the NDS naming environment to store service names and addresses of Oracle7 Server databases. This lets an NDS user view the entire network under a single NDS directory tree. You can use native name services in addition to or instead of Oracle Names or the TNSNAMES.ORA file.

If the NDS Authentication Adapter is also used, a single login can access a multi-server and multi-database network.

Additional Information See:

Oracle Advanced Networking Option Administrator's Guide for more information about the Native Naming Adapter

"Using the NDS Authentication Adapter" for more information about the NDS Authentication Adapter

Novell NetWare documentation for further information about NDS

Oracle7 Getting Started for NetWare

To connect with the NDS Native Naming Adapter:

Install and configure the NDS Native Naming Adapter and SQL*Net 2.3.3 on your client.

When you configure the NDS Naming Adapter, add NOVELL to the NAMES.DIRECTORY_PATH parameter in the SQLNET.ORA file:

NAMES.DIRECTORY_PATH = (NOVELL, TNSNAMES, ONAMES) 



 Additional Information

See the Oracle Advanced Networking Option Administrator's Guide for other optional parameters.

Install and configure SQL*Net 2.3.3 for NetWare on your server.
Log into the NDS tree.
Open SQL*Plus on your client.
Enter the following command to access an Oracle7 Server for NetWare database:
```
CONNECT username/password@database_object_name
```
where database_object_name identifies the Oracle7 Server in NDS.

Prev Next

Library

Product

Contents

Index

Using the Advanced Networking Option

Setting Up Network Security and Single Sign-On for Windows NT and Windows 95

Configuring the Kerberos Authentication Adapter

Configuring the SecurID Authentication Adapter

Configuring the CyberSAFE Authentication Adapter

Setting Up for Network Security and Single Sign-On for Windows 3.1x

Configuring the CyberSAFE Authentication Adapter

Configuring the Kerberos Authentication Adapter

Using the Oracle Kerberos Utility

Configuring the SecurID Authentication Adapter

Using the NDS Native Naming Adapter Note The NDS Native Naming Adapter is shipped as a part of SQL*Net. To use the NDS Authentication Adapter, you must run NetWare 4.1 or above with NDS.

Setting Up Network Security and Single Sign-On for
Windows NT and Windows 95

Using the NDS Native Naming Adapter

Note The NDS Native Naming Adapter is shipped as a part of SQL*Net. To use the NDS Authentication Adapter, you must run NetWare 4.1 or above with NDS.