test

Deployment Example 2: Federation Using SAML v2

Chapter 14 Installing and Configuring Web Policy Agents

This chapter contains detailed information about the following groups of tasks:

14.1 Creating Web Agent Profiles on the Federation Manager Servers

Use the following as your check list for creating Web Agent profiles on the Federation Manager servers:

  1. Create the UrlAccessAgent.properties file on Federation Manager 1.

  2. Create the UrlAccessAgent.properties file on Federation Manager 2.

ProcedureTo Create the UrlAccessAgent.properties File on Federation Manager 1

  1. Log into the Federation Manager 1 host.

  2. Generate an encrypted password:


    # /opt/SUNWam/fm/bin/ampassword  -i /var/opt/SUNWam/fm/war_staging --hash 11111111
BeUPgddAimR404ivWY6HPQ==

    Make note of this encrypted password. You will use this password as the UrlAccessAgent encrypted password which is similar to a shared secret used by other web containers.

  3. Go to the following directory:


    /var/opt/SUNWam/fm/federation/users

  4. Create a file that contains the UrlAccessAgent encrypted password.


    # vi UrlAccessAgent.properties
password=BeUPgddAimR404ivWY6HPQ==

    Save the file.

  5. Restart the Federation Manager 1 server.


    # /opt/SUNWwbsvr/https-FederationManager-1.siroe.com
# ./stop; ./start

ProcedureTo Create the UrlAccessAgent.properties File on Federation Manager 2

  1. Log into the Federation Manager 2 host.

  2. Generate an encrypted password:


    # /opt/SUNWam/fm/bin/ampassword  -i /var/opt/SUNWam/fm/war_staging --hash 11111111
BeUPgddAimR404ivWY6HPQ==

    Make note of this encrypted password. You will use this password as the UrlAccessAgent encrypted password which is similar to a shared secret used by other web containers.

  3. Go to the following directory:


    /var/opt/SUNWam/fm/federation/users

  4. Create a file that contains the UrlAccessAgent encrypted password.


    # vi UrlAccessAgent.properties
password=BeUPgddAimR404ivWY6HPQ==

    Save the file.

  5. Restart the Federation Manager 2 server.


    # /opt/SUNWwbsvr/https-FederationManager-2.siroe.com
# ./stop; ./start

14.2 Installing Web Server 3 and Web Policy Agent 3

For this part of the deployment, you must have the JES 5 installer and Web Policy Agent installer mounted on the host Protected Resource 1. See the section 2.2 Downloading and Mounting the Java Enterprise System 2005Q4 Installer in this manual.

Use the following as your checklist for installing Web Server 3 and Web Policy Agent 3:

  1. Install Web Server 3 on Protected Resource 3.

  2. Install Web Policy Agent 3.

ProcedureTo Install Web Server 3 on Protected Resource 3

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

  2. Start the Java Enterprise System installer with the -nodisplay option.


    # cd /mnt/Solaris_sparc 
# ./installer -nodisplay

  3. When prompted, provide the following information:


    Welcome to the Sun Java(TM) Enterprise System; 
serious software made  simple... 
<Press ENTER to Continue>

    Press Enter. 

    		 

    <Press ENTER to display the Software 
License Agreement>

    Press Enter. 

    		 

    Have you read, and do you accept, all of 
the termsof the preceding Software 
License Agreement [No]

    Enter y.

    		 

    Please enter a comma separated list of 
languages you would like supported with 
this installation [8]

    Enter 8 for “English only.” 

    		 

    Enter a comma separated list of products to 
install,or press R to refresh the list  []

    Enter 3 to select Web Server.

    		 

    Press "Enter" to Continue or Enter a 
comma separated list of products to deselect... [1]

    Press Enter. 

    		 
    Enter 1 to upgrade these shared components 
and 2 to cancel  [1]

    You are prompted to upgrade shared components only if the installer detects that an upgrade is required. 

    Enter 1 to upgrade shared components.

    		 

    Enter the name of the target 
installation directory for each product: 
Web Server [/opt/SUNWwbsvr] :

    Accept the default value. 

    		 

    System ready for installation 
Enter 1 to continue [1]

    Enter 1.

    		 

    1. Configure Now - Selectively override defaults or 
express through  
2. Configure Later - Manually configure following 
installation 
 Select Type of Configuration [1]

    Enter 1.

    		 

    Common Server Settings  
Enter Host Name [ProtectedResource-3]

    Accept the default value. 

    		 

    Enter DNS Domain Name [siroe.com]

    Accept the default value. 

    		 

    Enter IP Address [192.18.72.151]

    Accept the default value. 

    		 

    Enter Server admin User ID [admin]

    Accept the default value. 

    		 

    Enter Admin User's Password 
(Password cannot be less than 8 characters) 
[]

    For this example, enter 11111111.

    		 

    Confirm Admin User's Password []

    Enter the same password to confirm it. 

    		 

    Enter System User [root]

    Accept the default value. 

    		 

    Enter System Group [root]

    Accept the default value. 

    		 

    Enter  Server Admin User ID 
[admin]

    Accept the default value. 

    		 

    Enter Admin User's Password []

    For this example, enter 11111111.

    		 

    Enter Host Name 
[ProtectedResource-3.siroe.com]

    Accept the default value. 

    		 

    Enter Administration Port [8888]

    Accept the default value. 

    		 

    Enter Administration Server User ID 
[root]

    Accept the default value. 

    		 

    Enter System User ID [webservd]

    Enter root.

    		 

    Enter System Group [webservd]

    Enter root.

    		 

    Enter HTTP Port [80]

    Enter 2080.

    		 

    Enter content Root [/opt/SUNWwbsvr/docs]

    Accept the default value. 

    		 

    Do you want to automatically start 
Web Serverwhen system re-starts.(Y/N)    [N]

    Accept the default value. 

    		 

    Ready to Install
1. Install 2. Start Over 3. Exit Installation
What would you like to do [1]

    First, see the next numbered (Optional) step. When ready to install, enter 1.

  4. (Optional) During installation, you can monitor the log to watch for installation errors. Example:

    # cd /var/sadm/install/logs

    # tail —f Java_Enterprise_System_install.B xxxxxx

  5. Upon successful installation, enter ! to exit.

  6. Verify that the Web Server is installed properly.

    1. Start the Web Server administration server to verify it starts with no errors.

      # cd /opt/SUNWwbsvr/https-admserv

      # ./stop; ./start

    2. Run the netstat command to verify that the Web Server ports are open and listening.


      # netstat -an | grep 8888
  *.8888			*.*			0		0	49152		0	LISTEN

    3. Go to the Web Server URL.

      http://ProtectedResource-3.siroe.com:8888

    4. Log in to the Web Server using the following information:

      Username

      admin

      Password

      11111111

      You should be able to see the Web Server console. You can log out of the console now.

    5. Start the Protected Resource 3 instance.


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

    6. Run the netstat command to verify that the Web Server ports are open and listening.


      # netstat -an | grep 2080
  *.2080			*.*			0		0	49152		0	LISTEN

    7. Go to the instance URL.

      http://ProtectedResource-3.siroe.com:1080

      You should see the default Web Server index page.

ProcedureTo Install Web Policy Agent 3

Before You Begin
Caution – Caution –

If the Web Policy Agent installer is hosted on the same system where you are installing the Web Policy Agent, you can disregard this warning.

If the installer is hosted on a system other than the local system where you are installing the Web Policy Agent, you must start an X-display session on the system that hosts the installer. You must use an X-display program such as Reflections X or VNC even though you use the command-line installer. This is a known problem with this version of the Web Policy Agent. For more information about this known problem, see http://docs.sun.com/app/docs/doc/819-2796/6n52flfoq?a=view#adtcd.

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

  2. Download the Java System Web Policy Agents 2.2 package from the following website:

    http://www.sun.com/download/products.xml?id=434ed995

  3. Unpack the downloaded package.

    In this example, the package was downloaded into the directory /temp.


    # cd /temp
# gunzip sun-one-policy-agent-2.2-es6-solaris_sparc.tar.gz
# tar —xvof sun-one-policy-agent-2.2-es6-solaris_sparc.tar

  4. Start the Web Policy Agents installer.

    # ./setup -nodisplay

  5. When prompted, provide the following information:


    When you are ready, press Enter to continue. 
<Press ENTER to Continue>

    Press Enter. 

    		 

    Press ENTER to display the Sun Software 
License Agreement

    Press Enter. 

    		 

    Have you read, and do you accept, all of 
the terms of the preceding Software License 
Agreement [no] y

    Enter y.

    		 

    Install the Sun Java(tm) System Access Manager 
Policy Agent in this directory [/opt] :

    Accept the default value. 

    		 

    Enter information about the server instance this 
agent will protect. 
Host Name [ProtectedResource-3.siroe.com]:

    Accept the default value. 

    		 

    Web Server Instance Directory []:

    Enter  


    /opt/SUNWwbsvr/
https-ProtectedResource-9.siroe.com


    Web Server Port [80]:    :

    Enter 2080.

    		 

     Web Server Protocol [http]

    Enter https.

    		 

    Agent Deployment URI [/amagent]:

    Accept the default value. 

    		 

    Enter the Sun Java(tm) System Access Manager
Information for this Agent.
Primary Server Host [ProtectedResource-3.siroe.com] :

    For this example, enter the external-facing load balancer host name. Example: LoadBalancer-3.example.com 


    Primary Server Port [1080]

    Enter the load balancer HTTP port number. For this example, enter 3443.

    		 

    Primary Server Protocol [http]:

    Enter https.

    		 

    Primary Server Deployment URI [/amserver]:

    Enter /federation.

    		 

    Primary Console Deployment URI [/amconsole] :

    Enter /federation.

    		 

    Failover Server Host [] :

    Accept the default value. 

    		 

    Agent-Access Manager Shared Secret:

    Enter the amldapuser password that was entered when Access Manager was installed. For this example, enter 11111111 .

    		 

    Re-enter Shared Secret:

    Enter the 11111111 password again to confirm it.

    		 

    CDSSO Enabled [false]:

    Accept the default value. 

    		 

    Press "Enter" when you are ready to continue.

    First, see the next (Optional) numbered step. When you are ready to start installation, press Enter. 

  6. (Optional) During installation, you can monitor the log to watch for installation errors. Example:


    # cd /var/sadm/install/logs
# tail —f var/sadm/install/logs/
Sun_Java_tm__System_Access_Manager_Policy_Agent_install.Bxxxxxxxx

  7. Restart the Web Server. 


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

    Examine the Web Server log for startup errors.


    # /opt/SUNWwbsvr/https-ProtectedResource-3.siroe.com/logs
# vi errors

14.3 Completing the Web Policy Agent 3 Installation

Use the following as your checklist for completing the Web Policy Agent 3 installation:

  1. Edit the AMAgent.Properties file.

  2. Verify that Web Policy Agent 3 is working properly.

  3. Import the root CA certificate into the Web Server 3 key store.

  4. Verify that Web Policy Agent 3 can access the Federation Manager load balancer.

ProcedureTo Edit the AMAgent.Properties File

  1. Log in to as a root user to Federation Manager 1 host.

  2. Edit the AMAgent.properties file.


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

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


      com.sun.am.policy.am.username = UrlAccessAgent
com.sun.am.policy.am.password = BeVPgddAimR404ivWY6HPQ==
com.sun.am.policy.agents.config.do_sso_only = true

    2. Add the following properties to the original file:


      com.sun.am.ignore.naming.service = true

    3. (Optional) Set the debug property as in this example:


      com.sun.am.log.level = all:5

      Save the file.

  3. Restart Web Server 3.

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

Procedure To Verify that Web Policy Agent 3 is Working Properly

  1. Go to the following URL:

    http://ProtectedResource-3.siroe.com:2080

  2. Log in to Access Manager using the following information:

    Username

    spuser

    Password

    spuser

    You should see the default index.html page for Web Server 3.

ProcedureTo Import the Root CA Certificate into the Web Server 3 Key Store

The Web Policy Agent on Protected Resource 3 connects to Federation Manager servers through Load Balancer 9. The load balancer is SSL-enabled, so the agent must be able to trust the load balancer SSL certificate in order to establish the SSL connection. To do this, import the root CA certificate that issued the Load Balancer 3 SSL server certificate into the Web Policy Agent certificate store.

Before You Begin

Obtain the root CA certificate, and copy it to the Protected Resource 3 host . Copy the certificate into the file /export/software/ca.cert.

  1. Copy the root CA certificate to Protected Resource 3.

  2. Open a browser, and go to the Web Server 3 administration console.

    http://ProtectedResource-3.siroe.com:8888

  3. Log in to the Web Server 3 console using the following information:

    User Name:

    admin

    Password:

    11111111

  4. In the Select a Server field, select ProtectedResource-3.siroe.com, and then click Manage.

    Tip –

    If a “Configuration files have not been loaded” message is displayed, it may be because the Web Server instance that is being accessed through the administration server has had its configuration files manually edited. This is the case when the Web Policy Agent is installed. The mirror configuration files are different from the current configuration files. In order to be sure the changes are not lost, you must apply the changes. First click Apply, and then click Apply Changes. The configuration files are read, and the server is stopped and restarted.

  5. Click the Security tab.

  6. On the Initialize Trust Database page, enter a Database Password.

    Enter the password again to confirm it, and then click OK.

  7. In the left frame, click Install Certificate and provide the following information, and then click OK:

    Certificate For:

    Choose Trusted Certificate Authority (CA).

    Key Pair File Password:

    password

    Certificate Name:

    rootCA.cert

    Message in this File:

    /export/software/ca.cert

  8. Click Add Server Certificate.

  9. Click Manage Certificates.

    The root CA Certificate name rootCA.cert is included in the list of certificates.

  10. Click the Preferences tab.

  11. Restart Web Server 3.

    On the Server On/Off page, click Server Off. When the server indicates that the administration server is off, click Server On.

  12. Restart Web Server 3.

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

ProcedureTo Verify that Web Policy Agent 3 Can Access the Federation Manager Load Balancer

  1. Go to the Protected Resource 3 URL:


    http://ProtectedResource-3.siroe.com:2080/index.html

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

    User Name:

    spuser

    Password:

    spuser

    The policy agent redirects the request, and the URL changes to https://LoadBalancer-9.siroe.com:3443/federation/UI/Login. The default Sun ONE Web Server page is displayed. This verifies that the web policy agent is properly configured to access the Federation Manager load balancer.

14.4 Installing Web Server 4 and Web Policy Agent 4

For this part of the deployment, you must have the JES 5 installer and Web Policy Agent installer mounted on the host Protected Resource 1. See the section 2.2 Downloading and Mounting the Java Enterprise System 2005Q4 Installer in this manual.

Use the following as you checklist for installing Web Server 4 and Web Policy Agent 4:

  1. Install Web Server 4 on Protected Resource 4.

  2. Install Web Policy Agent 4.

ProcedureTo Install Web Server 4 on Protected Resource 4

  1. As a root user, log into the Protected Resource 4 host.

  2. Start the Java Enterprise System installer with the -nodisplay option.


    # cd /mnt/Solaris_sparc 
# ./installer -nodisplay

  3. When prompted, provide the following information:


    Welcome to the Sun Java(TM) Enterprise System; 
serious software made  simple... 
<Press ENTER to Continue>

    Press Enter. 

    		 

    <Press ENTER to display the Software 
License Agreement>

    Press Enter. 

    		 

    Have you read, and do you accept, all of 
the termsof the preceding Software 
License Agreement [No]

    Enter y.

    		 

    Please enter a comma separated list of 
languages you would like supported with 
this installation [8]

    Enter 8 for “English only.” 

    		 

    Enter a comma separated list of products to 
install,or press R to refresh the list  []

    Enter 3 to select Web Server.

    		 

    Press "Enter" to Continue or Enter a 
comma separated list of products to deselect... [1]

    Press Enter. 

    		 
    Enter 1 to upgrade these shared components 
and 2 to cancel  [1]

    You are prompted to upgrade shared components only if the installer detects that an upgrade is required. 

    Enter 1 to upgrade shared components.

    		 

    Enter the name of the target 
installation directory for each product: 
Web Server [/opt/SUNWwbsvr] :

    Accept the default value. 

    		 

    System ready for installation 
Enter 1 to continue [1]

    Enter 1.

    		 

    1. Configure Now - Selectively override defaults or 
express through  
2. Configure Later - Manually configure following 
installation 
 Select Type of Configuration [1]

    Enter 1.

    		 

    Common Server Settings  
Enter Host Name [ProtectedResource-4]

    Accept the default value. 

    		 

    Enter DNS Domain Name [siroe.com]

    Accept the default value. 

    		 

    Enter IP Address [192.18.72.152]

    Accept the default value. 

    		 

    Enter Server admin User ID [admin]

    Accept the default value. 

    		 

    Enter Admin User's Password 
(Password cannot be less than 8 characters) 
[]

    For this example, enter 11111111.

    		 

    Confirm Admin User's Password []

    Enter the same password to confirm it. 

    		 

    Enter System User [root]

    Accept the default value. 

    		 

    Enter System Group [root]

    Accept the default value. 

    		 

    Enter  Server Admin User ID 
[admin]

    Accept the default value. 

    		 

    Enter Admin User's Password []

    For this example, enter 11111111.

    		 

    Enter Host Name 
[ProtectedResource-4.siroe.com]

    Accept the default value. 

    		 

    Enter Administration Port [8888]

    Accept the default value. 

    		 

    Enter Administration Server User ID 
[root]

    Accept the default value. 

    		 

    Enter System User ID [webservd]

    Enter root.

    		 

    Enter System Group [webservd]

    Enter root.

    		 

    Enter HTTP Port [80]

    Enter 2080.

    		 

    Enter content Root [/opt/SUNWwbsvr/docs]

    Accept the default value. 

    		 

    Do you want to automatically start 
Web Serverwhen system re-starts.(Y/N)    [N]

    Accept the default value. 

    		 

    Ready to Install
1. Install 2. Start Over 3. Exit Installation
What would you like to do [1]

    First, see the next numbered (Optional) step. When ready to install, enter 1.

  4. (Optional) During installation, you can monitor the log to watch for installation errors. Example:

    # cd /var/sadm/install/logs

    # tail —f Java_Enterprise_System_install.B xxxxxx

  5. Upon successful installation, enter ! to exit.

  6. Verify that the Web Server is installed properly.

    1. Start the Web Server administration server to verify it starts with no errors.

      # cd /opt/SUNWwbsvr/https-admserv

      # ./stop; ./start

    2. Run the netstat command to verify that the Web Server ports are open and listening.


      # netstat -an | grep 8888
  *.8888			*.*			0		0	49152		0	LISTEN

    3. Go to the Web Server URL.

      http://ProtectedResource-4.siroe.com:8888

    4. Log in to the Web Server using the following information:

      Username

      admin

      Password

      11111111

      You should be able to see the Web Server console. You can log out of the console now.

    5. Start the Protected Resource 4 instance.


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

    6. Run the netstat command to verify that the Web Server ports are open and listening.


      # netstat -an | grep 2080
  *.2080			*.*			0		0	49152		0	LISTEN

    7. Go to the instance URL.

      http://ProtectedResource-4.siroe.com:1080

      You should see the default Web Server index page.

ProcedureTo Install Web Policy Agent 4

Before You Begin
Caution – Caution –

If the Web Policy Agent installer is hosted on the same system where you are installing the Web Policy Agent, you can disregard this warning.

If the installer is hosted on a system other than the local system where you are installing the Web Policy Agent, you must start an X-display session on the system that hosts the installer. You must use an X-display program such as Reflections X or VNC even though you use the command-line installer. This is a known problem with this version of the Web Policy Agent. For more information about this known problem, see http://docs.sun.com/app/docs/doc/819-2796/6n52flfoq?a=view#adtcd.

  1. As a root user, log into the Protected Resource 4 host.

  2. Download the Java System Web Policy Agents 2.2 package from the following website:

    http://www.sun.com/download/products.xml?id=434ed995

  3. Unpack the downloaded package.

    In this example, the package was downloaded into the directory /temp.


    # cd /temp
# gunzip sun-one-policy-agent-2.2-es6-solaris_sparc.tar.gz
# tar —xvof sun-one-policy-agent-2.2-es6-solaris_sparc.tar

  4. Start the Web Policy Agents installer.

    # ./setup -nodisplay

  5. When prompted, provide the following information:


    When you are ready, press Enter to continue. 
<Press ENTER to Continue>

    Press Enter. 

    		 

    Press ENTER to display the Sun Software 
License Agreement

    Press Enter. 

    		 

    Have you read, and do you accept, all of 
the terms of the preceding Software License 
Agreement [no] y

    Enter y.

    		 

    Install the Sun Java(tm) System Access Manager 
Policy Agent in this directory [/opt] :

    Accept the default value. 

    		 

    Enter information about the server instance this 
agent will protect. 
Host Name [ProtectedResource-4.siroe.com]:

    Accept the default value. 

    		 

    Web Server Instance Directory []:

    Enter  


    /opt/SUNWwbsvr/
https-ProtectedResource-4.siroe.com


    Web Server Port [80]:    :

    Enter 2080.

    		 

     Web Server Protocol [http]

    Accept the default value. 

    		 

    Agent Deployment URI [/amagent]:

    Accept the default value. 

    		 

    Enter the Sun Java(tm) System Access Manager
Information for this Agent.
Primary Server Host [ProtectedResource-9.siroe.com] :

    For this example, enter the load balancer host name. Example: LoadBalancer-9.siroe.com 


    Primary Server Port [1080]

    Enter the load balancer HTTP port number. For this example, enter 3443.

    		 

    Primary Server Protocol [http]:

    Enter https.

    		 

    Primary Server Deployment URI [/amserver]:

    Enter /federation.

    		 

    Primary Console Deployment URI [/amconsole] :

    Enter /federation.

    		 

    Failover Server Host [] :

    Accept the default value. 

    		 

    Agent-Access Manager Shared Secret:

    Enter the amldapuser password that was entered when Access Manager was installed. For this example, enter 11111111 .

    		 

    Re-enter Shared Secret:

    Enter the 11111111 password again to confirm it.

    		 

    CDSSO Enabled [false]:

    Accept the default value. 

    		 

    Press "Enter" when you are ready to continue.

    First, see the next (Optional) numbered step. When you are ready to start installation, press Enter. 

  6. (Optional) During installation, you can monitor the log to watch for installation errors. Example:


    # cd /var/sadm/install/logs
# tail —f var/sadm/install/logs/
Sun_Java_tm__System_Access_Manager_Policy_Agent_install.Bxxxxxxxx

  7. Restart the Web Server. 


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

    Examine the Web Server log for startup errors.


    # /opt/SUNWwbsvr/https-ProtectedResource-4.siroe.com/logs
# vi errors

14.5 Completing the Web Policy Agent 4 Installation

Use the following as your checklist for completing the Web Policy Agent 4 installation:

  1. Edit the AMAgent.Properties file.

  2. Verify that Web Policy Agent 4 is working properly.

  3. Import the root CA certificate into the Web Server 4 key store.

  4. Verify that Web Policy Agent 4 can access the Federation Manager load balancer.

ProcedureTo Edit the AMAgent.Properties File

  1. Log in to as a root user to Federation Manager 1 host.

  2. Edit the AMAgent.properties file.


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

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


      com.sun.am.policy.am.username = UrlAccessAgent
com.sun.am.policy.am.password = BeVPgddAimR404ivWY6HPQ==
com.sun.am.policy.agents.config.do_sso_only = true

    2. Add the following properties to the original file:


      com.sun.am.ignore.naming.service = true

    3. (Optional) Set the debug property as in this example:


      com.sun.am.log.level = all:5

      Save the file.

  3. Restart Web Server 4.

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

Procedure To Verify that Web Policy Agent 4 is Working Properly

  1. Go to the following URL:

    http://ProtectedResource-4.siroe.com:2080

  2. Log in to Access Manager using the following information:

    Username

    spuser

    Password

    spuser

    You should see the default index.html page for Web Server 4.

ProcedureTo Import the Root CA Certificate into the Web Server 4 Key Store

The Web Policy Agent on Protected Resource 4 connects to Federation Manager servers through Load Balancer 9. The load balancer is SSL-enabled, so the agent must be able to trust the load balancer SSL certificate in order to establish the SSL connection. To do this, import the root CA certificate that issued the Load Balancer 3 SSL server certificate into the Web Policy Agent certificate store.

Before You Begin

Obtain the root CA certificate, and copy it to the Protected Resource 4 host. Copy the certificate into the file /export/software/ca.cert.

  1. Copy the root CA certificate to Protected Resource 4.

  2. Open a browser, and go to the Web Server 4 administration console.

    http://ProtectedResource-4.siroe.com:8888

  3. Log in to the Web Server 4 console using the following information:

    User Name:

    admin

    Password:

    11111111

  4. In the Select a Server field, select ProtectedResource-4.siroe.com, and then click Manage.

    Tip –

    If a “Configuration files have not been loaded” message is displayed, it may be because the Web Server instance that is being accessed through the administration server has had its configuration files manually edited. This is the case when the Web Policy Agent is installed. The mirror configuration files are different from the current configuration files. In order to be sure the changes are not lost, you must apply the changes. First click Apply, and then click Apply Changes. The configuration files are read, and the server is stopped and restarted.

  5. Click the Security tab.

  6. On the Initialize Trust Database page, enter a Database Password.

    Enter the password again to confirm it, and then click OK.

  7. In the left frame, click Install Certificate and provide the following information, and then click OK:

    Certificate For:

    Choose Trusted Certificate Authority (CA).

    Key Pair File Password:

    password

    Certificate Name:

    rootCA.cert

    Message in this File:

    /export/software/ca.cert

  8. Click Add Server Certificate.

  9. Click Manage Certificates.

    The root CA Certificate name rooCA.cert is included in the list of certificates.

  10. Click the Preferences tab.

  11. Restart Web Server 4.

    On the Server On/Off page, click Server Off. When the server indicates that the administration server is off, click Server On.

  12. Restart Web Server 4.

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

ProcedureTo Verify that Web Policy Agent 4 Can Access the Federation Manager Load Balancer

  1. Go to the Protected Resource 4 URL:


    http://ProtectedResource-4.siroe.com:2080/index.html

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

    User Name:

    spuser

    Password:

    spuser

    The policy agent redirects the request, and the URL changes to https://LoadBalancer-9.siroe.com:3443/federation/UI/Login. The default Sun ONE Web Server page is displayed. This verifies that the web policy agent is properly configured to access the Federation Manager load balancer.

14.6 Configuring the Web Policy Agents Load Balancer

Load Balancer 11 can be located in a less-secured zone, and handles traffic for the Web Policy Agents.

Load Balancer 11 is configured for simple persistence so that browser requests from the same IP address will always be directed to the same Web Policy Agent instance . This guarantees that the requests from the same user session will always be sent to the same Web Policy Agent instance. This is important from the performance perspective. Each Web Policy Agent must validate the user session and evaluate applicable policies. The results are subsequently cached on the individual Web Policy Agent to improve the performance. If no load balancer persistence is set, and the same user's requests are spread across two agents, then each agent must build up its own cache. To do so, both agents must validate the session and evaluate policies. This effectively doubles the workload on the Access Manager servers, and cuts the overall system capacity by half. The problem becomes even more acute as the number of Web Policy Agents increases further.

As a general rule, in situations where each Web Policy Agent instance is protecting identical resources, some form of load balancer persistence is highly recommended for the performance reasons. The actual type of persistence may vary when a different load balancer is used, as long as it achieves the goal of sending the requests from the same user session to the same Web Policy Agent instance.

Use the following as your checklist for configuring the Web Policy Agents load balancer:

ProcedureTo Configure the Web Policy Agents Load Balancer

  1. Go to URL for the Big IP load balancer login page and log in.

    https://ls-f5.siroe.com

  2. Log in using the following information:

    User name:

    username

    Password:

    password

  3. Request an SSL Certificate for Load Balancer 11.

    1. Log in to the BIG-IP load balancer.

    2. Click Proxies in the left pane.

    3. Click the Cert Admin tab, and then click the “Generate New Key Pair/ Certificate Request” button.

    4. In the Create Certificate Request page, provide the following information:

      Key Identifier:

      LoadBalancer-11.siroe.com

      Organization:

      siroe.com

      Domain Name:

      LoadBalancer-11.siroe.com

      Email Address:

      jdoe@siroe.com

    5. Click the Generate Request button.

    6. In the Generate Request page, copy the request that looks similar to this:


      -----BEGIN CERTIFICATE REQUEST-----
UbM77e50M63v1Z2A/5O5MA0GCSqGSIb3DQEOBAU
AMF8xCzAJBgNVBAYTAlVTMSAwHgYDVQQKExdSU0
EgRGF0YSBTZWN1cml0eSwgSW5jLjEuMCwGA1UEC
xMlU2VjdXJlIFNlcnZlciBDZXJ0aWZpY2F0aW9u
IEF1dGhvcml0eTAeFw0wMTA4MDIwMDAwMDBaFw0
wMzA4MDIyMzU5NTlaMIGQMQswCQYDVQQGEwJVUz
ERMA8GA1UECBMIVmlyZ2luaWExETAPBgNVBAcUC
FJpY2htb25kMSAwHgYDVQQKFBdDYXZhbGllciBU
ZWxlcGhvYm9uZGluZy5jYXZ0ZWwuY29tMIGfMA0
GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC8x/1dxo
2YnblilQLmpiEziOqb7ArVfI1ymXo/MKcbKjnY2
-----END CERTIFICATE REQUEST-----

    7. Paste this text into a request form provided by a root certificate authority (CA) such as Verisign or Thwarte.

      See the certificate authority website such as http://www.verisign.com/ or http://www.thawte.com/ for detailed instructions on submitting a certificate request.

  4. After you receive the certificate from the issuer, install the SSL Certificate.

    1. In the BIG-IP load balancer console, click the Cert Admin tab.

    2. On the Cert Admin tab, click Install Certificate.

    3. In the Install SSL Certificate page, paste the certificate text you received from the certificate issuer. Example:


      -----BEGIN CERTIFICATE REQUEST-----
UbM77e50M63v1Z2A/5O5MA0GCSqGSIb3DQEOBAU
AMF8xCzAJBgNVBAYTAlVTMSAwHgYDVQQKExdSU0
EgRGF0YSBTZWN1cml0eSwgSW5jLjEuMCwGA1UEC
xMlU2VjdXJlIFNlcnZlciBDZXJ0aWZpY2F0aW9u
IEF1dGhvcml0eTAeFw0wMTA4MDIwMDAwMDBaFw0
wMzA4MDIyMzU5NTlaMIGQMQswCQYDVQQGEwJVUz
ERMA8GA1UECBMIVmlyZ2luaWExETAPBgNVBAcUC
FJpY2htb25kMSAwHgYDVQQKFBdDYXZhbGllciBU
ZWxlcGhvYm9uZGluZy5jYXZ0ZWwuY29tMIGfMA0
GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC8x/1dxo
2YnblilQLmpiEziOqb7ArVfI1ymXo/MKcbKjnY2
-----END CERTIFICATE REQUEST-----

    4. Click Install Certificate.

  5. Create a Pool.

    A pool contains all the backend server instances.

    1. Open the Configuration Utility.

      Click “Configure your BIG-IP (R) using the Configuration Utility.”

    2. In the left pane, click Pools.

    3. On the Pools tab, click the Add button.

    4. In the Add Pool dialog, provide the following information:

      Pool Name

      federation_web_agents

      Load Balancing Method

      Round Robin

      Resources

      192.18.72.151:2080 (for Protected Resource 3)

      192.18.72.152:2080 (for Protected Resource 4)

      Click Done.

  6. Configure the load balancer for simple persistence.

    1. In the left frame, click Pools.

    2. Click the name of the pool you want to configure.

      In this example, federation_web_agents.

    3. Click the Persistence tab.

    4. On the Persistence tab, under Persistence Type, select the Simple.

    5. Set the timeout interval.

      In the Timeout field, enter 300 seconds.

      Click Apply.

  7. Add a Virtual Server.

    If you encounter Javascript errors or otherwise cannot proceed to create a virtual server, try using Microsoft Internet Explorer for this step.

    1. In the left frame, Click Virtual Servers.

    2. On the Virtual Servers tab, click the Add button.

    3. In the Add Virtual Server dialog box, provide the following information:

      Address

      192.18.69.14 (for LoadBalancer-11.siroe.com )

      Service

      5080

      Click Next.

    4. Continue to click Next until you reach the Select Physical Resources dialog box.

      Pool

      federation_web_agents

    5. In the Pool Selection dialog box, assign the Pool (federation_web_agents) that you have just created.

    6. Click the Done button.

  8. Create proxies.

    1. In the left frame, click Proxies.

    2. On the Proxies tab, click Add.

    3. In the Add Proxy page, provide the following information:

      Proxy Type:

      Mark the SSL checkbox.

      Proxy Address:

      192.18.69.14

      Proxy Service:

      6443

      Destination Address:

      192.18.69.14

      Destination Service:

      5080

      SSL Certificate:

      LoadBalancer-11.siroe.com

      SSL Key:

      LoadBalancer-11.siroe.com

      Server SSL Certificate:

      LoadBalancer-11.siroe.com

      Server SSL Key:

      LoadBalancer-11.siroe.com

      Click Done.

  9. Add Monitors.

    1. Click the Monitors tab, and then click the Add button.

      In the Add Monitor dialog provide the following information:

      Name:

      WebAgent-http

      Inherits From:

      Choose http.

    2. Click Next.

      In the Configure Basic Properties page, click Next.

    3. In the Configure ECV HTTP Monitor, in the Send String field, enter the following:

      GET /launch.html

      Click Next.

    4. In the Destination Address and Service (Alias) page, click Done.

      On the Monitors tab, the monitor you just added is now contained in the list of monitors.

    5. Click the Basic Associations tab.

      Look for the IP addresses for ProtectedResource-3:2080 and ProtectedResourece-4:1080.

    6. Mark the Add checkbox for ProtectedResource-3 and ProtectedResource-4.

    7. At the top of the Node column, choose the monitor that you just added, WebAgent-http.

    8. Click Apply.

ProcedureTo Configure the Web Policy Agents to Work with the Web Policy Agents Load Balancer

In this procedure you modify the AMAgent.properties file. Map Protected Resource 3 and Protected Resource 4 to Load Balancer 11.

  1. Log in as a root user to Protected Resource 3.


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

  2. Use a text editor to modify the AMAgent.properties file.

    For this property:

    com.sun.am.policy.agents.config.notenforced_list

    append the following to the end of the value string :

    http://ProtectedResource-3.siroe.com:1080/launch.html http://LoadBalancer-11.siroe.com:90/launch.html

  3. Set the following properties:


    com.sun.am.load_balancer.enable = true
com.sun.am.policy.agents.config.override_protocol = true
com.sun.am.policy.agents.config.override_host = true
com.sun.am.policy.agents.config.override_port = true
com.sun.am.policy.agents.config.agenturi.prefix =
https://LoadBalancer-11.siroe.com:6443/amagent
com.sun.am.policy.agents.config.fqdn.map = 
[LoadBalancer-11.siroe.com|LoadBalancer-11.siroe.com]
com.sun.am.policy.agents.config.fqdn.default = 
LoadBalancer-11.siroe.com

    Save the file.

  4. Restart Web Server 3 on Protected Resource 3.


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

  5. Log in as a root user to Protected Resource 4.


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

  6. Use a text editor to modify the AMAgent.properties file.

    For this property:

    com.sun.am.policy.agents.config.notenforced_list

    append the following to the end of the value string :

    http://ProtectedResource-4.siroe.com:1080/launch.html http://LoadBalancer-11.siroe.com:90/launch.html

  7. Set the following properties:


    com.sun.am.load_balancer.enable = true
com.sun.am.policy.agents.config.override_protocol = true
com.sun.am.policy.agents.config.override_host = true
com.sun.am.policy.agents.config.override_port = true
com.sun.am.policy.agents.config.agenturi.prefix =
https://LoadBalancer-11.siroe.com:6443/amagent
com.sun.am.policy.agents.config.fqdn.map = 
[LoadBalancer-11.siroe.com|LoadBalancer-11.siroe.com]
com.sun.am.policy.agents.config.fqdn.default = 
LoadBalancer-11.siroe.com

    Save the file.

  8. Restart Web Server 4 on Protected Resource 4.


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

ProcedureTo Verify that the Web Policy Agents Load Balancer is Working Properly

  1. In a browser, go to the following URL:

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

    The load balancer redirects the request to the Access Manager login page.

  2. Log in to the Access Manager console using the following information:

    Username

    spuser

    Password

    spuser

    If the default Web Server index.html page is displayed, then the load balancer is configured properly.

  3. Verify that Load Balancer 11 monitors are monitoring the Web Servers properly.

    1. Log in as a root user to Protected Resource 3.

    2. Run the tail command. 


      # cd /opt/SUNWwbsvr/https-ProtectedResource-3.siroe.com/logs
# tail -f access

      If you see frequent entries similar to this one:


      192.18.69.18 - - [06/Oct/2006:13:53:07 -0700] "GET /launch.html" 200 8526

      then the custom monitor is configured properly. If you do not see "GET /launch.html", then you must troubleshoot the load balancer configuration.

    3. Log in as root to Protected Resource 4.

    4. Run the tail command. 


      # cd /opt/SUNWwbsvr/https-ProtectedResource-4.siroe.com/logs
# tail -f access

      If you see frequent entries similar to this one:


      192.18.69.18 - - [06/Oct/2006:13:53:07 -0700] "GET /launch.html" 200 8526

      then the custom monitor is configured properly. If you do not see "GET /launch.html", then you must troubleshoot the load balancer configuration.

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.