test

Deployment Example 2: Federation Using SAML v2

14.7 Configuring the Web Policy Agents Load Balancer to Participate in SAMLv2 Protocols

Use the following as your checklist for configuring the Web Policy Agents load balancer to participate in SAMLv2 protocols:

  1. Enable the Web Policy Agents load balancer to use SAMLv2 protocols.

  2. Verify that the Web Policy Agents load balancer uses SAMLv2 protocols.

ProcedureTo Enable the Web Policy Agents Load Balancer to Use SAMLv2 Protocols

  1. As a root user, log in to the Protected Resource 3 host.

  2. Go to the following directory:


    /etc/opt/SUNWam/agents/es6/config/
_opt_SUNWwbsvr_https-ProtectedResource-3.siroe.com

  3. Make a backup of AMAgent.properties, and then set the following properties:


    com.sun.am.policy.am.login.url = 
https://LoadBalancer-9.siroe.com:3443/federation/saml2/
jsp/spSSOInit.jsp?metaAlias=/sp&idpEntityID=loadbalancer-3.example.com

  4. Add the following property:


    com.sun.am.policy.agents.config.url.redirect.param = RelayState

    Save the file.

  5. As a root user, log in to the Protected Resource 4 host.

  6. Go to the following directory:


    /etc/opt/SUNWam/agents/es6/config/
_opt_SUNWwbsvr_https-ProtectedResource-4.siroe.com

  7. Make a backup of AMAgent.properties, and then set the following properties:


    com.sun.am.policy.am.login.url = 
https://LoadBalancer-9.siroe.com:3443/federation/saml2/
jsp/spSSOInit.jsp?metaAlias=/sp&idpEntityID=loadbalancer-3.example.com

  8. Add the following property:


    com.sun.am.policy.agents.config.url.redirect.param = RelayState

    Save the file.

  9. Restart the Protected Resource 3 host.


    # cd /opt/SUNWwbsvr/https-ProtectedResource-3.siroe.com
# ./stop; ./start

  10. Restart the Protected Resource 4 host.


    # cd /opt/SUNWwbsvr/https-ProtectedResource-4.siroe.com
# ./stop; ./start

ProcedureTo Verify that the Web Policy Agents Load Balancer Uses SAMLv2 Protocols

  1. Go to the following URL:


    https://LoadBalancer-11.siroe.com:6443/index.html

  2. Log into the Access Manager console using the following information:

    User Name:

    idpuser

    Password:

    idpuser

    The Web Server default index.html page is displayed.