15.3 Registering an OAM Agent Using the Console

The registration procedure for WebGate or programmatic Access Client is the same. You can register an OAM-type agent before you deploy it.

Users with valid Administrator credentials can perform the following task to register a WebGate using the Oracle Access Management Console.

See Also:

After agent registration, you can change the communication mode of the OAM Server if needed. Communication between the agent and server continues to work as long as the WebGate mode is at least at the same level as the OAM Server mode or higher. See Securing Communication.

Note:

You use the same procedure to register a programmatic Access Client. The version is the same as the SDK used to create the Access Client.

See Also:

Oracle Fusion Middleware Upgrade Guide for Oracle Identity and Access Management for details about Identity Connect

Before you begin, confirm that at least one OAM Server is running in the same mode as the agent to be registered.

  1. In the Oracle Access Management Console, click Application Security at the top of the window.

  2. In the Application Security console, select Create WebGate from the Agents menu.

  3. On the Create WebGate page, enter required details (those with an *) to register this Agent.

    Note:

    If you are creating an OAM 10g Agent, also see Registering and Managing 10g WebGates with Access Manager 11g.

  4. Protected Resource List: In this table, enter individual resource URLs to be protected by this Agent, as shown in Table 15-1.

  5. Public Resource List: In this table, enter individual resource URLs to be public (not protected), as shown in Table 15-1.

  6. Auto Create Policies: Check to create a fresh Application Domain and policies (or clear and use the same host identifier as another WebGate and share policies (Table 15-1)).

  7. Click Apply to submit the registration.

    You may also close the page without applying changes, if applicable.

  8. Click the Download button to download the generated artifacts.

    Downloaded artifacts are located in the $DOMAIN_HOME/output/$Agent_name folder.

  9. 10g WebGate: See Registering and Managing 10g WebGates with Access Manager 11g and:

    1. Proceed as needed for your environment (Registering and Managing 10g WebGates with Access Manager 11g):

      Existing WebGate: Perform Step 8, then go to Configuring Centralized Logout for Sessions Involving 11g WebGates.

      New WebGate: Go to "Locating and Installing the Latest 10g WebGate for Access Manager 11g".

  10. Copy the artifacts as follows (or install WebGate with the same specifications, then copy artifacts), including any Simple or Cert mode files. For example, Open mode files include:

    Agent & Artifacts Artifacts

    11g WebGate/Access Client

    ObAccessClient.xml and cwallet.sso

    From the AdminServer (Console) host: $DOMAIN_HOME/output/$Agent_Name/

    To the Agent host: $11gWG_install_dir/WebGate/config

    10g WebGate/Access Client

    ObAccessClient.xml

    Note: Go to Registering and Managing 10g WebGates with Access Manager 11g before completing this task.

    From the AdminServer (Console) host: $DOMAIN_HOME/output/$Agent_Name/

    To the Agent host: $10gWG_install_dir/oblix/lib/

  11. Verify Registration: These are similar to steps in "Validating Agent Registration using the Oracle Access Management Console".

    1. Under Agents in Application Security, search and confirm the Agent name is listed.

    2. Confirm the Agent's page contains the appropriate information.

    3. Auto Create Policies: Confirm the Application Domain was generated, the host identifier was created for the application, and that resources were created in the Application Domain and associated with the host identifier.

    4. Perform further tests, as described in "Verifying Authentication and Access After Remote Registration".

  12. Proceed as needed for your deployment: