|Oracle® Access Manager Installation Guide
The WebPass is second in the sequence of Oracle Access Manager components to install. This chapter explains how to install the WebPass and configure your Web server to work with it. For details, see:
The WebPass is a Web server plug-in that shuttles information back and forth between the Web server and the Identity Server as described in the Oracle Access Manager Introduction. (A WebPass must also be installed with each Policy Manager as discussed in "Identity System Guidelines".)
Installing a WebPass follows a similar sequence and includes a number of the same procedures as the Identity Server installation. However, the following exceptions apply to WebPass:
WebPass does not communicate with the directory server. Therefore, no directory server details are requested during WebPass installation.
WebPass does communicate with a Web server.
Be sure to choose the proper package for your Web server and platform. The Web server configuration must be updated. Oracle recommends that you accept the automatic update during WebPass installation.
WebPass cannot reside in the same directory as the Identity Server (or Policy Manager). For example, if the Identity Server is installed in C:\OracleAccessManager\, consider installing the WebPass in C:\OracleAccessManager\WebComponent.
Install the WebPass and specify a unique identifier for WebPass (different than Identity Server identifier), as described in .
Conclude with the appropriate procedures for your installation. For example:
The installation process is similar regardless of the installation method you choose and your operating system. Differences for specific operating systems and Web servers are noted within the installation procedures when appropriate. Again, any caveats are identified and may be skipped when they do not apply to your environment.
During WebPass installation on a Windows system, you will not be asked to specify a Windows Service name. Rather than starting and stopping a WebPass service, you will start and stop the WebPass Web server.
If you plan to install multiple WebPass instances, pay close attention to the following items:
Oracle Access Manager supports one WebPass for each Web server instance. This means that each WebPass instance must have its own Web server instance.
All WebPass instances must be installed with the same transport security mode as the Identity Server to which they are connecting.
You must have at least one WebPass instance installed before you can perform the Identity Server setup described in Chapter 6, "Setting Up the Identity System".
After the first Identity Server is set up, you can install any number of WebPass instances. For each additional WebPass, you must add information about the new instance in the Identity System Console. For details and instructions, see the Oracle Access Manager Identity and Common Administration Guide.
Before you begin installing the WebPass, check the tasks in Table to ensure they have been completed. Failure to complete prerequisites may adversely affect your Oracle Access Manager installation
Table 5-1 WebPass Installation Prerequisites Checklist
|Checklist||WebPass Installation Prerequisites|
Review and complete all prerequisites and requirements that apply to your environment, as described in Part I, "Installation Planning and Prerequisites"
Complete all activities in Chapter 4, "Installing the Identity Server".
Review Web server specific details in:
Refer to your completed installation preparation worksheets as you install the WebPass. The procedures in this sequence cover both GUI and console method. Following the program launch, one set of procedures will be provided because the sequence is similar.
The following procedures must be completed to install the WebPass:
Choosing the installation method and initiating the process as described in "Starting the Installation"
Choosing a transport security option for WebPass as discussed in "Specifying a Transport Security Mode"
Identifying WebPass configuration details as described in "Specifying WebPass Configuration Details"
Performing automatic Web server configuration updates as explained in "Updating the WebPass Web Server Configuration"
Completing the process as discussed in "Finishing the WebPass Installation"
Be sure to choose the appropriate installation package for your Web server and review Web server-specific details as described in Table 5-1.
Log in as a user with administrator privileges.
Locate the WebPass installer (including any Identity System Language Packs you want to install) in the temporary directory you created.
Launch the WebPass installer for your preferred platform, installation method, and Web server. For example:
Dismiss the Welcome screen by clicking Next.
Respond to the question about administrator rights based upon your platform. For example:
Choose the installation destination, then click Next. For example:
A summary identifies the installation directory and required disk space and asks you to make a note of this information for future reference.
Write the installation directory name, if needed, then click Next to continue.
You are notified that the WebPass is being installed and kept informed about the status of the process, which may take several seconds. On Windows systems, the Microsoft Managed Interfaces are also being configured.
You are asked to specify a transport security mode to use between the WebPass and Identity Server. At this point, you cannot return to restate the installation directory.
Transport security between all Identity System components (Identity Servers and WebPass instances) must match: either all open, all Simple mode, or all Cert. For more information, see "Securing Oracle Access Manager Component Communications".
Choose the same transport security mode for the WebPass as you did for the Identity Server.
When you specify Simple or Cert, you will be asked for additional information later. You are asked now for WebPass configuration details.
Now, you are asked to enter a unique name to use for this WebPass, which will appear in the Identity System Console after setup.
Each WebPass must have a unique name that identifies it. The WebPass name you specify cannot contain any blank spaces and must uniquely identify this WebPass in the Identity System Console and LDAP directory.
You are also asked to identify the DNS hostname and port number of a Identity Server with which this WebPass should communicate. In addition, you may be asked to specify additional information about the transport security mode you selected when you selected either Simple or Certificate mode only.
Enter a unique name for this WebPass that adheres to the preceding guidelines. For example:
Enter the DNS hostname of the Identity Server with which this WebPass should communicate. For example:
Enter the port number of the Identity Server with which this WebPass should communicate, then click Next. For example:
Perform the following operations according to the transport security mode you chose earlier.
Open: Skip to .
Simple: Specify and confirm the Pass Phrase to authenticate between the Identity Server and WebPass, click Next, then continue with .
Certificate: Continue with step 5.
Certificate: Indicate if you are requesting or installing a certificate, then click Next and continue as follows:
If you are requesting a certificate, enter information about your organization, click Next, issue the request to your CA, and continue with step 6.
If you are installing a certificate, skip to step 8.
Request Certificate: Click Yes if your certificates are available (otherwise click No), then click Next and continue with step 8.
If certificates are not ready, complete the installation. When you receive the certificates, copy these to the \WebPass_install_dir\identity\oblix\config directory and restart the WebPass Web server.
With an IIS Web server, consider using
You are notified that the WebPass is being configured, which may take a few seconds. The information has been saved and you may not return to previous screens to restate details.
You are now asked to update the WebPass Web server configuration.
Your WebPass Web server must be configured with product-related configuration information to use the WebPass component. You can direct this update to occur either automatically or manually. Updating the Web server configuration:
On Sun Web servers a configuration update involves updating the obj.conf and magnus.conf files.
On IIS Web servers a configuration update involves updating the Web server directly by adding the ISAPI filter and creating extensions required by Oracle Access Manager. For more information, see Chapter 19, "Installing Web Components for the IIS Web Server".
On Apache Web servers a configuration update involves updating the httpd.conf file. For more information, see Chapter 16, "Configuring Apache v1.3-based Web Servers for Oracle Access Manager" or Chapter 17, "Configuring Web Components for Apache v2-based Web Servers".
Oracle recommends automatically updating your Web server configuration. However, instructions for manual configuration are included.
Click Yes to automatically update your Web server, then click Next. For example:
Most Web Servers: Specify the absolute path of the directory containing the Web server configuration files.
IIS Web Servers: The process begins immediately and may take more than a minute. For more information, see Chapter 19, "Installing Web Components for the IIS Web Server".
A screen appears when the Web server configuration has been updated.
Sun Web Servers: Apply the changes in the Web server Administration console before you continue.
Stop the WebPass Web server instance, then stop the Identity Server service.
Start the Identity Server service, then start the WebPass Web server instance.
With IIS, using
Click Next to dismiss the announcement, then continue with .
ReadMe information appears.
Click No when asked if you want to proceed with the automatic update, then click Next.
ReadMe information appears along with a new screen to assist you in manually setting up your Web server for Oracle Access Manager.
Return to the WebPass installation screen and click Next to finish the installation.
The ReadMe information provides details about documentation and Oracle.
Review the ReadMe information.
Click Next to complete the installation.
Continue with the following procedures, as needed:
Native POSIX Thread Library: When installing Oracle Access Manager Web components for use with NPTL, there is no need to set the environment variable LD_ASSUME_KERNEL to 2.4.19.
Manually Configuring Your Web Server if you did not do this automatically during WebPass installation.
If you do not want the installation wizard to update your Web server configuration during WebPass installation, you must do it manually before you set up the Identity Server.
You complete step 1 only if needed to display online instructions.
Launch your Web browser, and open the following file, if needed. For example:
where \WebPass_install_dir is the directory where you installed the WebPass and langTag is a language, en-us, for example.
Select the appropriate Web server interface configuration protocol from the table on the screen
Follow all instructions specific to your Web server type and:
Make a back up copy of any file that you are required to modify during Web server set up, so it is available if you need to start over.
Some setups launch a new browser window or require you to launch a Command window to input information, so ensure that you return to and complete all original setup instructions to enable your Web server to recognize the appropriate Oracle Access Manager files.
If you accidentally close the window, you can open the \WebPass_install_dir\identity\oblix\apps\common\docs\config.htm file in a browser window and click the appropriate link again.
Continue with the appropriate task for your environment when you finish your Web server update. For example:
Security-Enhanced Linux: Errors might be reported in Web server logs/console when starting a Web server on Linux distributions that have stricter SELinux policies in place after installing an Oracle Access Manager Web component. You can avoid these errors by running appropriate
chcon commands for the installed Web component before restarting the Web server.
After installation, you must establish communications between WebPass and its Identity Server when the Web server restarts using the following procedure.
Stop the WebPass Web server instance.
Stop then restart Identity Server service.
Start the WebPass Web server instance.
A good way to ensure that the WebPass is installed correctly is to complete the following procedure.
Make sure your Identity Server and WebPass Web server are running.
Navigate to the Identity System Console from your browser by specifying the following URL. For example:
Do not select any link on the Identity System landing page, because the system has not yet been set up. See Chapter 6, "Setting Up the Identity System".