Setting Up the Oracle Adaptive Access Manager Base Environment

2-2 Oracle Fusion Middleware Administrators Guide for Oracle Adaptive Access Manager ■ Importing the OAAM Snapshot ■ Importing IP Location Data ■ Importing Transaction Definitions ■ Enabling Components and Features ■ Setting the Time Zone Used for All Time Stamps in the Administration Console

2.3 Setting Up CLI Environment

The Oracle Adaptive Access Manager Command-Line Interface CLI scripts enable users to perform various tasks instead of using the Oracle Adaptive Access Manager Administration Console. For information on setting up the CLI environment, see Section 29.2, Setting Up the CLI Environment.

2.4 Setting Up Encryption and Database Credentials for Oracle Adaptive Access Manager

Encryption is used to protect data within Oracle Adaptive Access Manager from unauthorized access. The process uses methods and a key or keys to encode plain text into a non-readable form. A key is required to decrypt the encrypted information and make it readable again. Authorized persons who possess the key can decrypt information that is encrypted with the same key. This section provides instructions to set up encryption and database credentials for Oracle Adaptive Access Manager.

2.4.1 Overview of the Process

An overview for setting up encryption and database credentials is provided in this section.

2.4.1.1 Setting up Encryption

Setting up encryption involves the following steps: ■ Ensure the secret keys a.k.a symmetric keys for both the configuration value and database are available. If you do not have a secret key, generate an encoded symmetric key using the genEncodedKey command. ■ Encode the key using the base64encode option of the encodeKey command. This step is not required if the genEncodedKey command was used to generate the key. ■ Use the Fusion Middleware Control to add the encoded secret key to an alias in the Credential Store Framework in the domain where Oracle Adaptive Access Manager is installed. A credential store is a repository to store user namepassword or generic credentials a certificate. The value of using a credential store is that the application does not store passwords in clear text and does not have to invent its own solutions for protecting passwords, allowing administrators and developers alike to work with a consistent credential repository. Setting Up the Oracle Adaptive Access Manager Environment for the First Time 2-3

2.4.1.2 Configuring Database Credentials in the Credential Store Framework

Configuring database credentials in the Credential Store Framework involves the following steps: ■ Use the Fusion Middleware Control to add database credentials user name and password in the Credential Store Framework in the domain where Oracle Adaptive Access Manager is installed. These credentials are used by the Oracle Adaptive Access Manager command-line utilities. ■ Configure the properties files that are used by the Oracle Adaptive Access Manager CLI utilities with details of the WebLogic administration server and Oracle Adaptive Access Manager database. For information on the credential store, refer to Managing the Credential Store in the Oracle Fusion Middleware Application Security Guide.

2.4.2 Prerequisites

Prerequisites for setting up encryption and database credentials for Oracle Adaptive Access Manager are: 1. If you do not have access to the Oracle Adaptive Access Manager installation folder, make sure Oracle Adaptive Access Manager 11g is configured with Fusion Middleware Control while creating the domain. 2. If you have access to the Oracle Adaptive Access Manager installation folder then make sure you have access to running the command-line scripts in the MW_ HOME\IDM_ORACLE_HOME\oaam\cli folder. 3. Make sure Sun JDK is installed and check that the java command is in the path by executing the java command.

2.4.3 Setting up Secret Key for Encrypting Configuration Values

To set up the secret key for encrypting configuration values, follow the steps in this section:

1. Go to the Oracle Adaptive Access Manager command-line folder MW_

HOME\IDM_ORACLE_HOME\oaam\cli.

2. Create a file config_secret_key.file and add the secret key to the file by

entering: tobase64=secret-key Note: If you are upgrading from Oracle Adaptive Access Manager 10.1.4.5 to Oracle Adaptive Access Manager 11g, you can skip Section 2.4.3, Setting up Secret Key for Encrypting Configuration Values, , Section 2.4.4, Setting Up Secret Key for Encrypting Database Values, and Section 2.4.5, Generating an Encoded Secret Key, since the Upgrade Assistant automatically migrates the secret keys from Oracle Adaptive Access Manager 10.1.4.5 to the Credential Store Framework in Oracle Adaptive Access Manager 11g.