59.4 Preparing for Integration With SharePoint Server

The ISAPI 10g WebGate must be installed on the same computer as the SharePoint Server. Other components in this integration can reside on the same host as the WebGate or any other computer in your deployment (Solaris, Linux, or Windows platforms).

Tasks in the following procedure are required for all integration scenarios described in this chapter.

After installing and testing Microsoft components, perform steps here to install Access Manager for your integration. This task applies to both integration scenarios in this chapter. To avoid repetition, information here is not repeated elsewhere.

A different host can be set up for Active Directory or some other directory service. If both Access Manager and SharePoint Server are set up for different instances of Active Directory, both instances must belong to the same Active Directory domain.

Prerequisites

Install and test Microsoft components described in "Required Microsoft Components".

To prepare for integration with SharePoint Server

  1. Install Oracle Identity Management and Access Manager as described in the .

  2. Register a 10g WebGate for IIS Web server with Access Manager:

    1. Log in to the Oracle Access Management Console. For example: http://host:port/oamconsole.

    2. Click Application Security at the top of the window.

    3. In the Launch Pad tab, click SSO Agent Registration in the Quick Start Wizards section.

    4. Select WebGate as the agent type and click Next.

    5. Set the agent version to 10g and enter required details (those with an *):

      • Name
      • SharePoint user name and password
      • Security mode (Agent host must match OAM Server)
      • Auto Create Policies (Checked)

      Note:

      Do not specify a Base URL.

    6. Protected Resource List: In this table, enter individual resource URLs to be protected by this OAM Agent.

    7. Public Resource List: In this table, enter individual resource URLs to be public (not protected).

    8. Click Apply to submit the registration, check the Confirmation window for the location of generated artifacts, then close the window.

  3. Proceed as follows:

  4. Locate and download the 64-bit ISAPI WebGate installer as follows:

    1. Go to Oracle Fusion Middleware 11gR1 Software Downloads at:

      https://www.oracle.com/technology/software/products/middleware/htdocs/fmw_11_download.html

    2. Click Accept License Agreement, at the top of the page.

    3. From the Access Manager Webgates (10.1.4.3.0) row, click the download link for the desired platform and follow on-screen instructions.

    4. Store the WebGate installer in the same directory as any 10g (10.1.4.3) Access System Language Packs you want to install.

  5. Launch the WebGate installer for your platform, installation mode, and Web server.

    Follow these steps:

    1. Follow on-screen prompts.

    2. Provide Administrator credentials for the Web server.

    3. Language Pack—Choose a Default Locale and any other Locales to install, then click Next.

    4. WebGate installation begins (IISImpersonationModule.dll will be installed in WebGate_install_dir\access\Oblix\apps\Webgate\bin\).

  6. Before updating the Web server configuration, copy WebGate artifacts from the Admin Server to the computer hosting the WebGate.

    1. On the computer hosting the Oracle Access Management Console (AdminServer), locate and copy ObAccessClient.xml (and any certificate artifacts):

      $DOMAIN_HOME/output/$Agent_Name/

      • ObAccessClient.xml
      • password.xml (if needed)
      • aaa_key.pem (your private key generated by openSSL)
      • aaa_cert.pem (signed certificates in PEM format)

    2. On the OAM Agent host, add the artifacts to the WebGate path. For example:

      • WebGate_install_dir/access/oblix/lib/ObAccessClient.xml
      • WebGate_install_dir/access/oblix/config

    3. Restart the WebGate Web server.

    4. (Optional.) Restart the OAM Server that is hosting this Agent. This step is recommended but not required.

  7. Proceed as needed to complete this integration within your environment: