Web Services Application Integration

2 Setting Up the Oracle Adaptive Access Manager Environment for the First Time 2-1 2 Setting Up the Oracle Adaptive Access Manager Environment for the First Time All tasks in this book presume that you have Oracle Adaptive Access Manager 11g installed with initial configuration completed as described in the Oracle Fusion Middleware Installation Guide for Oracle Identity Management. This chapter presents details on setting up the Oracle Adaptive Access Manager environment for first time users. For information on how to upgrade an existing Oracle Adaptive Access Manager 10g 10.1.4.5 to Oracle Adaptive Access Manager 11g Release 1 11.1.1.5.0, refer to the Oracle Fusion Middleware Upgrade Guide for Oracle Identity Management.

2.1 Installation and Configuration

The Oracle Fusion Middleware Installation Guide for Oracle Identity Management 11g Release 1 11.1.1 provides all installation and initial configuration details. Oracle Adaptive Access Manager is installed into an environment where you may install other Oracle Identity Management 11g components. The following Oracle Adaptive Access Manager-related components are deployed in a new WebLogic administration domain using the Oracle Fusion Middleware Configuration Wizard: ■ WebLogic Administration Server ■ Managed Server for Oracle Adaptive Access Manager ■ Oracle Adaptive Access Manager Console deployed on the Administration Server For information on how to install and configure Oracle Adaptive Access Manager, see the Oracle Fusion Middleware Installation Guide for Oracle Identity Management.

2.2 Setting Up the Oracle Adaptive Access Manager Base Environment

After installing and configuring Oracle Adaptive Access Manager, you must complete the following tasks to set up the initial base Oracle Adaptive Access Manager environment. Procedures are provided in the following sections: ■ Setting Up CLI Environment ■ Setting Up Encryption and Database Credentials for Oracle Adaptive Access Manager ■ Creating OAAM Users 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.