Skip to content

Latest commit

 

History

History
46 lines (34 loc) · 2.85 KB

connect-to-the-oracle-database-using-windows-authentication.md

File metadata and controls

46 lines (34 loc) · 2.85 KB
Raw
description title ms.custom ms.date ms.service ms.reviewer ms.suite ms.topic
Learn more about: Connect to the Oracle Database Using Windows Authentication
Connect to the Oracle Database Using Windows Authentication
06/08/2017
biztalk-server
article

Connect to the Oracle Database Using Windows Authentication

The [!INCLUDEadapteroracle] enables adapter clients to use Windows Authentication to establish a connection with the Oracle database. To use Windows Authentication, the adapter clients must specify “/” for user name and leave the password blank. For more information about connecting to the Oracle database using Windows Authentication, see Connect to Oracle Database in Visual Studio using the Consume Adapter Service.

To enable adapter clients to use Windows Authentication to connect to an Oracle database, you must perform the following tasks on the computer running the Oracle database.

  1. Make sure that the sqlnet.ora file on both the client and the server, available under ORACLE_BASE\ORACLE_HOME\network\admin\sqlnet.ora, has the following entry:

    SQLNET.AUTHENTICATION_SERVICES= (NTS)

  2. Connect to the Oracle database as SYSDBA.

  3. Create the Windows user as an external user in the Oracle database. Note that the user name must be in upper case.

    CREATE USER “OPS$<DOMAIN_NAME>\<USER_NAME\>” IDENTIFIED EXTERNALLY;

  4. Grant privileges to the user.

    GRANT CONNECT,RESOURCE TO “OPS$<DOMAIN_NAME>\<USER_NAME\>”;

  5. To enable the newly created user, logging in using Windows Authentication, to access the Oracle database artifacts, you can change the user’s schema to the SCOTT schema. You can add the following SQL command to the logon script that changes the user’s default schema to SCOTT when the user logs on.

    alter session set current_schema=SCOTT;

  6. Even though you changed the schema of the user to the SCOTT schema, you will still not be able to see the Oracle database artifacts while browsing and generating metadata using the [!INCLUDEadapteroracle_short]. This is because the newly created user does not have permissions for the SCOTT schema. Make sure you provided permission for the SCOTT schema to the newly created user.

See Also

Configure the Oracle Client for the Oracle Database adapter
Create a connection to the Oracle Database