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

ProcedureTo Verify that Authentication Through the Distributed Authentication User Interface 2 is Successful

Find a host that has direct network connectivity to Distributed Authentication User Interface 2 and the external facing load balancer of the Access Manager servers. One natural place is the AuthenticationUI–2 host machine itself.

  1. As a root user, log into the AuthenticationUI–2 host machine.

  2. Modify AMConfig.properties.

    1. Change to the classes directory.


      # cd /opt/SUNWwbsvr/https-AuthenticationUI-2.example.com/
        web-app/AuthenticationUI-2.example.com/distAuth/WEB-INF/classes
      

      Tip –

      Backup AMConfig.properties before you modify it.


    2. Set the values of the properties as follows.

      com.iplanet.am.naming.url=https://LoadBalancer-3.
        example.com:9443/amserver/namingservice
      com.iplanet.am.server.protocol=https
      com.iplanet.am.server.port=9443
    3. Save the file and close it.

  3. Restart the AuthenticationUI-2 host machine.


    # cd /opt/SUNWwbsvr/https-AuthenticationUI-2.example.com/bin
    # ./stopserv; ./startserv
    
  4. Access http://AuthenticationUI-2.example.com:1080/distAuth/UI/Login?goto= http://LoadBalancer-3.example.com:7070 from a web browser.

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

    Username

    amadmin

    Password

    4m4dmin1

    After successful authentication, you should be redirected to the index page for the Web Server in which Access Manager is deployed.

  6. Log out of the Access Manager console.