About DAC Authentication Modes

DAC Standalone Authentication Mode

DAC standalone authentication mode uses the DAC user account security model. DAC user account information is stored in the DAC repository. A DAC user with the Administrator role creates user accounts with the appropriate user names, passwords, and roles. The DAC administrator needs to distribute the user account information (name and password) to the users to enable them to log into the DAC Client and repository. In standalone mode, the DAC Server does not participate in user authentication.
Using the DAC standalone authentication mode, a user can connect to a DAC repository that is configured for either Fusion Middleware or standalone mode. However, when the DAC repository is in Fusion Middleware (Web) mode and the user is authenticated through standalone mode, the user cannot run ETLs, because the user cannot connect to the DAC Server. When standalone mode is used for both the user and DAC repository, connecting to the DAC Server is possible, and, therefore, ETLs can be run.

About the DAC Authentication File

The DAC authentication file is a cwallet.sso file and is used by the DAC Client and automation utilities to connect to the DAC repository. It contains the repository database schema owner and password and a DAC encryption key. An authentication file and a DAC repository have a one-to-one relationship.
The authentication file is automatically generated when the Oracle BI Applications Installer is run or when the BI domain is extended by running the install_dwtools.py installation script. When automatically generated, the authentication file is saved by default in <DAC_Config_Location>\conf-shared\security\repository.
The authentication file can also be created by a DAC user at the time of the first connection to the DAC repository. The first time users connect to a DAC repository, they must either specify an authentication file that was previously created or create a new authentication file. When creating a new authentication file, the user must specify the database schema owner and password.
A DAC administrator needs to distribute the authentication file to users who need access to the repository.

Logging Into DAC for the First Time as an Administrator

When you log into DAC for the first time, you must configure a connection to the DAC repository. DAC stores this connection information for subsequent logins.
The initial login process for an administrator varies depending on the authentication mode being used and whether an authentication file was already created.
If you are using Fusion Middleware authentication, the authentication file was created during the Oracle BI Applications set up and configuration process. You will need to know the location of this file when you log into DAC for the first time.
If you are using DAC standalone authentication, you will create an authentication file while logging into DAC for the first time. To do so, you will need to know the database schema owner and password.
Regardless of the authentication mode, an administrator must distribute the authentication file to all user accounts (those authenticated through DAC as well as through WebLogic Server) that need to access the specified DAC repository. For more information about the authentication file, see "About the DAC Authentication File".
To log in to DAC for the first time

1. Start the DAC Client by navigating to the <Domain_Home>\dac directory and double-clicking the startclient.bat file.
   The Login... dialog is displayed.
   
2. Click Configure.
3. In the Configuring... dialog, select Create Connection, and then click Next.
4. Enter the appropriate connection information:
   

   Field	Required Value
   Name	Enter a unique name for the connection to the DAC repository.
   Connection type	Select the type of database in which the DAC repository will be stored.
   Connection String, or Database name, or TNS Name, or Service Name	Select the database name or database account name of the DAC repository. If you are using: Oracle (OCI8), use the tnsnames entry. Oracle (Thin), use the service name. SQL Server, use the database name. DB2-UDB, use the connect string as defined in the DB2 configuration.
   Database Host	Enter the name of the machine where the DAC repository will reside.
   Database Port	Enter the port number on which the database listens. For example, for an Oracle database the default port is 1521, or for a SQL Server database the default port is 1433.
   DB URL (Optional)	Can be used to override the standard URL for this connection.
   DB Driver (Optional)	Can be used to override the standard driver for this connection.
   Authentication File	Click in this field to do one of the following: Select an existing authentication file. Proceed to step 5 for detailed instructions. Create a new authentication file. Proceed to step 6 for detailed instructions.
   SSL Trust Store File	(Optional) For deployments in Web mode, location of the SSL Trust Store file.
   SSL JKS Password File	(Optional) For deployments in Web mode, location of the SSL JKS password file.
   Log Level	Specifies a client log level for the client session. The logs are saved in <Domain_Home>\dac\log\client <client's logical connection name>.

5. To select an existing authentication file, do the following:
   
   1. Click in the Authentication File field.
   2. In the Authentication File dialog, select Choose existing authentication file, and click OK.
   3. Navigate to the appropriate directory, and select the appropriate cwallet.sso file. Click OK.
   4. In the Configuring... dialog, click Test Connection to confirm the connection works.
   5. Click Apply, and then click Finish.
      
      Note:

      A DAC administrator must distribute this authentication file to all user accounts that need to access this DAC repository.
6. To create a new authentication file, do the following:
   
   1. Click in the Authentication File field of the Configuring... dialog.
   2. In the Authentication File dialog, select Create authentication file, and click OK.
   3. Navigate to the directory where you want to save the new authentication file, and click OK.
   4. In the Create Authentication File dialog, enter the Table Owner Name and Password for the database where the repository will reside.
   5. Click Generate Random Encryption Key to generate an encryption key for the authentication file. The key is displayed in the Key field.
      Alternatively, you can enter a key in the Key field. The key must be at least 24 characters long.
   6. Click OK to close the Create Authentication File dialog.
   7. In the Configuring... dialog, click Test Connection to confirm the connection works.
      
      Note:

      You must distribute this authentication file to all user accounts that need to access this DAC repository.
7. Click Apply, and then click Finish
8. To log in using Web mode, do the following:
   
   1. In the Login... dialog, select the appropriate Connection from the drop-down list.
   2. Enter your User Name and Password.
      This must match the user name and password stored in the WebLogic Server identity store.
   3. Select FMW as the Authentication Type.
   4. If you want DAC to remember the password for this connection, select Remember Password.
   5. Click Login.
      The DAC Client is displayed.
9. To log in using DAC standalone mode, do the following:
   
   1. In the Login... dialog, select the appropriate Connection from the drop-down list.
   2. For a first-time login, you can enter any values in the User Name and Password fields, because the DAC repository that you just created does not contain any user names or passwords.
      A user account will be created with the user name and password you enter in this step. This user account is automatically assigned the Administrator role.
   3. Select DAC as the Authentication Type.
   4. If you want DAC to remember the password for this connection, select Remember Password.
   5. Click Login.
10. (Optional) To specify the DAC view and tab that you want to appear each time you log in, click Options.
11. If a DAC repository has not already been created, you will be prompted to create one. Click Yes.
    This process creates DAC repository tables.
    Depending on your database type, you may have the option to specify a tablespace.
    The Unicode check box is available for a repository on SQL Server or DB2 databases. Check the Unicode check box if your deployment requires a Unicode schema to be created.