test

Deployment Example 1: Access Manager 7.1 Load Balancing, Distributed Authentication UI, and Session Failover

ProcedureTo Configure the J2EE Policy Agent 1 to Access the Distributed Authentication User Interface

  1. Log in as a root user to the ProtectedResource–1 host machine.

  2. Change to the directory that contains the AMAgent.properties file.


    # cd /export/J2EEPA1/j2ee_agents/am_wl92_agent/agent_001/config
    Tip –

    Backup AMAgent.properties before you modify it.

  3. Set the following properties in AMAgent.properties.


    com.sun.identity.agents.config.login.url[0] =
   https://LoadBalancer-4.example.com:9443/distAuth/UI/Login?realm=users

  4. Save AMAgent.properties and close it.

  5. Restart the Application Server 1 managed instance.

    1. Change to the bin directory.


      # cd /usr/local/bea/user_projects/domains/ProtectedResource-1/bin

    2. Stop the managed instance.


      # ./stopManagedWebLogic.sh ApplicationsServer-1 t3://localhost:7001

    3. Start the managed instance.


      # ./startManagedWebLogic.sh ApplicationServer-1 t3://localhost:7001

  6. Log out of the ProtectedResource–1 host machine.

  7. Verify that the agent is configured properly.

    1. Access http://protectedresource-1.example.com:1081/agentsample/index.html, the sample application URL, from a web browser.

      The Sample Application Welcome page is displayed.

    2. Click the J2EE Declarative Security link.

    3. On the resulting page, click Invoke the Protected Servlet.

      You are redirected to the Distributed Authentication User Interface at https://loadbalancer-4.example.com:9443/distAuth/UI/Login.

    4. (Optional) Double-click the gold lock in the lower left corner of the browser.

      In the Properties page, you see the certificate for LoadBalancer–4.example.com.

    5. Log in to the Access Manager console as testuser1.

      Username

      testuser1

      Password

      password

      If you can successfully log in as testuser1 and the J2EE Policy Agent Sample Application page is displayed, user authentication worked through the Distributed Authentication User Interface and the agent is configured properly.

    6. Log out of the console.