9 Configuring Oracle Privileged Account Manager

This chapter explains how to configure Oracle Privileged Account Manager. It includes the following topics:

9.1 Overview

For an introduction to the Oracle Privileged Account Manager, see "Understanding Oracle Privileged Account Manager" in the Oracle Fusion Middleware Administrator's Guide for Oracle Privileged Account Manager.

9.2 Important Note Before You Begin

Before you start installing and configuring Oracle Identity and Access Management products in any of the scenarios discussed in this guide, note that IAM_Home is used to refer to the Oracle Home directory that includes Oracle Identity Manager, Oracle Access Management, Oracle Adaptive Access Manager, Oracle Entitlements Server, Oracle Identity Navigator, Oracle Privileged Account Manager, and Oracle Access Management Mobile and Social. You can specify any name for this Oracle Home directory.

9.3 Installation and Configuration Roadmap for Oracle Privileged Account Manager

Table 9-1 lists the tasks for installing and configuring Oracle Privileged Account Manager.

Table 9-1 Installation and Configuration Flow for Oracle Privileged Account Manager

No. Task Description

1

Review installation concepts in the Installation Planning Guide.

Read the Oracle Fusion Middleware Installation Planning Guide, which describes the process for various users to install or upgrade to Oracle Fusion Middleware 11g (11.1.2) depending on the user's existing environment.

2

Review the system requirements and certification documents to ensure that your environment meets the minimum installation requirements for the components you are installing.

For more information, see Section 2.1, "Reviewing System Requirements and Certification".

3

Obtain the Oracle Fusion Middleware Software.

For more information, see Section 3.2.1, "Obtaining the Oracle Fusion Middleware Software"

4

Review the Database requirements.

For more information, see Section 3.2.2, "Database Requirements".

5

Run Oracle Fusion Middleware Repository Creation Utility (RCU) to create and load the appropriate schemas for Oracle Identity and Access Management products.

For more information, see Section 3.2.3, "Creating Database Schema Using the Oracle Fusion Middleware Repository Creation Utility (RCU)".

Note: Oracle Privileged Account Manager schema must be created by a Database user with SYSDBA privileges.

6

Review WebLogic Server and Middleware Home requirements.

For more information, see Section 3.2.4, "WebLogic Server and Middleware Home Requirements".

7

Start the Oracle Identity and Access Management Installer.

For more information, see Section 3.2.6, "Starting the Oracle Identity and Access Management Installer".

8

Install the Oracle Identity and Access Management 11g software.

Oracle Privileged Account Manager is included in the Oracle Identity and Access Management Suite. You can use the Oracle Identity and Access Management 11g Installer to install Oracle Identity and Access Management Suite.

For more information, see Section 3.2.7, "Installing Oracle Identity and Access Management 11g Release 2 (11.1.2.2.0)".

9

Optional: Enable TDE in OPAM data store.

For more information, see Section 9.4, "Optional: Enabling TDE in Oracle Privileged Account Manager Data Store"

10

Run the Oracle Fusion Middleware Configuration Wizard to configure your Oracle Identity and Access Management products in a new or existing WebLogic domain.

For more information, see Section 9.5, "Configuring Oracle Privileged Account Manager and Oracle Identity Navigator in a New WebLogic Domain".

11

Upgrade the OPSS schema using Patch Set Assistant

For more information, see Section 3.2.9, "Upgrading OPSS Schema using Patch Set Assistant"

12

Configure the Database Security Store.

For more information, see Section 3.2.10, "Configuring Database Security Store for an Oracle Identity and Access Management Domain".

13

Complete the post-installation tasks.

Complete the following post-installation tasks:

9.4 Optional: Enabling TDE in Oracle Privileged Account Manager Data Store

Oracle Privileged Account Manager can operate with Oracle Database TDE (Transparent Data Encryption) mode. You can choose to either enable or disable the TDE mode. Oracle strongly recommends to enable the TDE mode for enhanced security.

This section includes the following topics:

9.4.1 Enabling TDE in the Database

For information about enabling Transparent Data Encryption (TDE) in the database for Oracle Privileged Account Manager, refer to the "Enabling Transparent Data Encryption" topic in Oracle Database Advanced Security Administrator's Guide.

For more information, see "Securing Stored Data Using Transparent Data Encryption" in the Oracle Database Advanced Security Administrator's Guide

After enabling TDE in the database for Oracle Privileged Account Manager, you must enable encryption in OPAM schema, as described in Section 9.4.2, "Enabling Encryption in OPAM Schema".

9.4.2 Enabling Encryption in OPAM Schema

To enable encryption in the OPAM schema, run the opamxencrypt.sql script with the OPAM schema user, using sqlplus or any other client.

IAM_HOME/opam/sql/opamxencrypt.sql

Example:

sqlplus DEV_OPAM/welcome1 @IAM_HOME/opam/sql/opamxencrypt.sql

9.5 Configuring Oracle Privileged Account Manager and Oracle Identity Navigator in a New WebLogic Domain

This topic describes how to configure Oracle Privileged Account Manager and Oracle Identity Navigator in a new WebLogic administration domain. It includes the following sections:

9.5.1 Deployment Environment

Perform the configuration in this topic if you want to configure Oracle Privileged Account Manager with Oracle Identity Navigator in a new WebLogic domain and then run the Oracle Identity Navigator discovery feature. This feature populates links to the product consoles for Oracle Identity Manager, Oracle Access Management, Oracle Adaptive Access Manager, and Oracle Privileged Account Manager. You can then access those product consoles from within the Oracle Identity Navigator interface, without having to remember the individual console URLs.

9.5.2 Components Deployed

Performing the configuration in this section deploys the Oracle Privileged Account Manager and Oracle Identity Navigator applications on a new WebLogic domain.

9.5.3 Dependencies

The configuration in this section depends on the following:

9.5.4 Procedure

Perform the following steps to configure Oracle Privileged Account Manager and Oracle Identity Navigator in a new WebLogic administration domain:

  1. Start the Oracle Fusion Middleware Configuration Wizard by running the IAM_HOME/common/bin/config.sh script (on UNIX), or IAM_HOME\common\bin\config.cmd (on Windows).

    The Welcome screen of the Oracle Fusion Middleware Configuration Wizard appears.

    Note:

    IAM_Home is used as an example here. You must run this script from your Oracle Identity and Access Management Home directory that contains Oracle Identity Manager, Oracle Access Management, Oracle Adaptive Access Manager, Oracle Entitlements Server, Oracle Privileged Account Manager, Oracle Access Management Mobile and Social, and Oracle Identity Navigator.

  2. On the Welcome screen, select Create a new WebLogic domain, and click Next. The Select Domain Source screen appears.

  3. On the Select Domain Source screen, ensure that the Generate a domain configured automatically to support the following products: option is selected. Select Oracle Privileged Account Manager - 11.1.2.0.0 [IAM_Home].

    Note:

    When you select the Oracle Privileged Account Manager - 11.1.2.0.0 [IAM_Home] option, the following options are also selected, by default:

    • Oracle Identity Navigator for Managed Server - 11.1.2.2.0 [IAM_Home]

    • Oracle Platform Security Service 11.1.1.0 [IAM_Home]

    • Oracle JRF 11.1.1.0 [oracle_common]

    Click Next. The Specify Domain Name and Location screen appears.

  4. Enter a name and a location for the domain to be created, and click Next. The Configure Administrator User Name and Password screen appears.

  5. Configure a user name and a password for the administrator. The default user name is weblogic. Click Next.

  6. The Configure Server Start Mode and JDK screen appears. Choose a JDK from the Available JDKs and select a WebLogic Domain Startup Mode. Click Next.

  7. On the Configure JDBC Component Schema screen, select a component schema, such as the OPAM Schema or the OPSS Schema, that you want to modify.

    You can set values for Schema Owner, Schema Password, Database and Service, Host Name, and Port. Click Next. The Test JDBC Component Schema screen appears. After the test succeeds, click Next. The Select Optional Configuration screen appears.

  8. On the Select Optional Configuration screen, you can configure the following:

    • Administration Server

    • Managed Servers, Clusters and Machines

    • Deployments and Services

    • RDBMS Security Store

    Select the desired options, and click Next.

  9. Optional: Configure the following Administration Server parameters:

    • Name

    • Listen address

    • Listen port

    • SSL listen port

    • SSL enabled or disabled

  10. Optional: Configure Managed Servers, as required.

  11. Optional: Configure Clusters, as required.

    For more information about configuring clusters for Oracle Identity and Access Management products, see the "Configuring High Availability for Oracle Identity and Access Management Components" topic in Oracle Fusion Middleware High Availability Guide.

  12. Optional: Assign Managed Servers to clusters, as required.

  13. Optional: Configure Machines, as needed. This step is useful when you want to run the Administration Server on one machine and Managed Servers on another physical machine.

    Tip:

    Before configuring a machine, use the ping command to verify whether the machine or host name is accessible.

  14. Optional: Assign the Administration Server to a machine.

  15. Optional: Select Deployments, such as applications and libraries, and Services to target them to a particular cluster or server.

  16. Optional: Configure RDBMS Security Store, as required.

  17. On the Configuration Summary screen, you can view summaries of your configuration for deployments, application, and service. Review the domain configuration, and click Create to start creating the domain.

A new WebLogic domain to support Oracle Privileged Account Manager and Oracle Identity Navigator is created in the MW_HOME\user_projects\domains directory (on Windows). On UNIX, the domain is created in the MW_HOME/user_projects/domains directory.

Note:

After configuring Oracle Privileged Account Manager in a new WebLogic administration domain, you must complete the procedure described in the following sections, before starting the servers:

9.6 Starting the Oracle WebLogic Administration Server

After installing and configuring Oracle Privileged Account Manager, you must start the Oracle WebLogic Administration Server, as described in Appendix C, "Starting the Stack".

9.7 Post-Installation Tasks

After installing and configuring Oracle Privileged Account Manager, you must run the opam-config.sh script (on UNIX), or opam-config.bat script (on Windows).

  • Before executing the script, ensure that the WebLogic Administration Server is running. For more information on starting the Oracle WebLogic Administration Server, see Appendix C, "Starting the Stack".

    Note:

    If you are extending a domain, ensure that the WebLogic Administration Server is restarted before running the opam-config.sh script (on UNIX), or opam-config.bat script (on Windows).

  • Set up ANT_HOME, ORACLE_HOME, JAVA_HOME and the permgen size.

    For example:

    On Windows:

    set ORACLE_HOME= ##set Oracle_Home here##
set ANT_HOME=MW_HOME\modules\org.apache.ant_1.7.1
set JAVA_HOME=MW_HOME\jdk160_14_R27.6.4-18
set ANT_OPTS=-Xmx512M -XX:MaxPermSize=512m

    On UNIX:

    set ORACLE_HOME ##set Oracle_Home here##
set ANT_HOME $MW_HOME/modules/org.apache.ant_1.7.1
set JAVA_HOME $MW_HOME/jdk160_14_R27.6.5-32
set ANT_OPTS "-Xmx512M -XX:MaxPermSize=512m"

    Note:

    On 64-bit platforms, when you install Oracle WebLogic Server using the generic jar file, JDK is not installed with Oracle WebLogic Server. You must install JDK separately, before installing Oracle WebLogic Server. In this case, you must specify the JAVA_HOME location accordingly.

  • Go to IAM_HOME/opam/bin directory and run the opam-config.sh script (on UNIX), or opam-config.bat script (on Windows). Provide the following information, when prompted:

    • Oracle WebLogic Administration username

    • Oracle WebLogic Administration password

    • Oracle WebLogic Administration Server URL

    • Oracle WebLogic Domain Name

      Note:

      Oracle WebLogic Domain Name is case sensitive. You must provide the same value that you defined during domain creation.

    • Oracle Middleware Home

      Note:

      Oracle Middleware Home is case sensitive. You must provide the same value that you defined during domain creation.

  • The log file for opam-config script will be created in MW_HOME/user_projects/domains/Domain_Name/opam-config.log.

    If the above directory does not exist, then the log file for opam-config script will be created in IAM_HOME/opam/config/opam-config.log.

    The log file location will be printed on the screen after the script is executed.

Note:

After running the opam-config.sh script (on UNIX), or opam-config.bat script (on Windows), you must restart the Oracle WebLogic Administration Server, as described in Appendix C, "Starting the Stack".

9.8 Starting the Managed Server

You must start the Oracle Privileged Account Manager Managed Server, as described in Appendix C, "Starting the Stack".

9.9 Assigning the Application Configurator Role to a User

After you complete the installation process, you do not have any users with administrator roles. You may select a user and grant that user the Application Configurator role by using Oracle Identity Navigator.

Note:

For more information, see "Assigning a Common Admin Role" in the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Navigator.

For information about the Administration Roles that the Application Configurator user can have, see "Administration Role Types" in the Oracle Fusion Middleware Administrator's Guide for Oracle Privileged Account Manager.

9.10 Optional: Setting Up Non-TDE Mode

Note:

Oracle Privileged Account Manager can operate with Oracle Database TDE (Transparent Data Encryption) mode. You can choose to either enable or disable the TDE mode. Oracle strongly recommends to enable the TDE mode for enhanced security.

If you want to disable TDE mode, you must set the flag tdemode to false.

Note:

The steps described in this section are required only if you choose to skip Section 9.4, "Optional: Enabling TDE in Oracle Privileged Account Manager Data Store".

Complete the following steps to disable TDE mode:

  1. Set the environment variables ORACLE_HOME and JAVA_HOME.

  2. Run the following script:

    On Windows:

    ORACLE_HOME\opam\bin\opam.bat -url OPAM_Server_URL -x modifyglobalconfig -propertyname tdemode -propertyvalue false -u OPAM_APPLICATION_CONFIGURATOR_USER -p Password

    where OPAM_Server_URL is of the form https://OPAM_Managed_Server_Hostname:OPAM_Managed_Server_SSL_port/opam

    On UNIX:

    ORACLE_HOME/opam/bin/opam.sh -url OPAM_Server_Url -x modifyglobalconfig -propertyname tdemode -propertyvalue false -u OPAM_APPLICATION_CONFIGURATOR_USER -p Password

    where OPAM_Server_URL is of the form https://OPAM_Managed_Server_Hostname:OPAM_Managed_Server_SSL_port/opam

Note:

TDE mode can be enabled or disabled at any point after installing and configuring Oracle Privileged Account Manager. For more information on changing the TDE mode at a later time, refer to the "Securing Data On Disk" topic in the Oracle Fusion Middleware Administrator's Guide for Oracle Privileged Account Manager.

9.11 Optional: Configuring OPAM Console

When the Application Configurator user logs in using the following URL:

http://<opam-managedserver-host>:<opam-managedserver-nonsslport>/oinav/opam

the Oracle Privileged Account Manager Console autodetects the connection settings for the Oracle Privileged Account Manager server, and the Oracle Privileged Account Manager Console is populated with content.

To modify the server connection settings, the Application Configurator user can go to the Configuration option on the left pane, and click on Server Connection. On the Server Connection tab, the user can provide a new host and port.

9.12 Verifying Oracle Privileged Account Manager

After completing the installation process, including post-installation steps, you can verify the installation and configuration of Oracle Privileged Account Manager as follows:

  1. Ensure that the Oracle Privileged Account Manager Server is up and running, using the following URL:

    https://<opam-managedserver-host>:<opam-managedserver-sslport>/opam

    You will be prompted to enter a username and password. Enter your WebLogic username and password. The following result should be displayed:

    {
  ServerState: {
    Status: "Oracle Privileged Account Manager Server is up!",
    StatusCode: 0
  },
  Requestor: "WebLogic_username",
  RequestorGroups: [
    "Administrators"
  ]
}

  2. Log in to the Administration Console for Oracle Privileged Account Manager using the URL:

    http://<opam-managedserver-host>:<opam-managedserver-nonsslport>/oinav/opam

    When you access this Administration Console running on the OPAM Managed Server, you are prompted to enter a user name and password. Note that you must have Administrator's role and privileges.

  3. Verify the Oracle WebLogic Server Administration Console. If the installation and configuration of Oracle Privileged Account Manager is successful, this console shows opam_server1 in the running mode, which is the default Managed Server.

  4. In the Domain Structure pane, click on Deployments. The following applications should be listed in the Deployments table, and the state must be Active:

    • oinav

    • opam

    • opamsessionmgr

9.13 Getting Started with Oracle Privileged Account Manager After Installation

After installing Oracle Privileged Account Manager, refer to the "Getting Started with Administering OPAM" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle Privileged Account Manager.