Federation Security Services Guide › Deploying Federation with the FSS Sample Application › Prerequisites for Using the FSS Sample Application (r12sp1 FSS Gd)

Prerequisites for Using the FSS Sample Application (r12sp1 FSS Gd)

Before you run the FSS sample application, you must satisfy the following requirements:

• SiteMinder requirements (SiteMinder r12.0 SP2 components recommended):
  • Install an LDAP or ODBC user directory and policy store
  • Install a SiteMinder Policy Server
  • Install a SiteMinder Web Agent

    The web server where the Web Agent is installed does not require an SSL port.

  • Ensure the Policy Server and Web Agent are configured properly and that you can protect a resource using any authentication scheme.

  Important! Core SiteMinder has to be functioning properly to run the sample application successfully.

• SiteMinder Federation Security Services requirements
  • Install the SiteMinder Policy Server.

    Important! If you choose to initialize a new policy store, the Policy Server installer will automatically import the affiliate objects contained in the ampolicy.smdif file. These objects are necessary for federation. If you use an existing policy store that you do not initialize, you will have to manually import the affiliate objects.To verify that the import is successful, log in to the FSS Administrative UI and click on Domains in the System tab. You should see the FederationWebServices domain object.

  • Install the SiteMinder Web Agent Option Pack on the same web server as the Web Agent. This is required because Federation Web Services, which is installed by the Web Agent Option Pack, has to run on the same system as ServletExec, the servlet engine being used with the sample application.
  • (Optional) If you want to see the assertion that is generated when you test single sign-on, you have to enable FSS trace logging so that the FWSTrace.log file is generated. You enable logging in the LoggerConfig.properties file, located in the directory web_agent_home/affwebservices/WEB-INF/classes.
  • Install and configure ServletExec.

    You should have received a license file called licensekey50.txt from CA Support. From this license file, copy the license key and enter it in the ServletExec License dialog of the ServletExec Administration Console.

  • Deploy Federation Web Services as a ServletExec web application.

    You do not have to setup the Federation Web Services Application; these tasks are done by the sample application. However, you do have to deploy Federation Web Services as a ServletExec web application. You deploy a web application using the ServletExec Administration Console.

    Note: For instructions on installing ServletExec, setting the license key, and deploying web applications, see New Atlanta Communication's ServletExec documentation.

  • Configure and enable a session store (SQL or Oracle ODBC database). Setup the database instance using a session server scheme file.

    For instructions on configuring a session server, see the SiteMinder Policy Server Installation Guide. To point the Policy Server to the session server after you have created it, see the SiteMinder Policy Server Administration Guide.

  Note: If you are using two separate systems, install all these components on both systems.

• Use the Perl interpreter shipped with the FSS sample application to run the application.
• Add the variable <NETE_PS_ROOT>\CLI\bin to the system PATH environment variable to invoke the Perl script to run the sample application.

  Important! Ensure that the Perl binary bundled with the Policy Server is the first or only such binary in the PATH so that the bundled Perl binary is invoked and not another Perl script.

• The user running the Perl script must have read/write permissions to the web server's document root directory.

Note: If your Federation Security Services system is communicating with a SiteMinder Federation Endpoint system, see the SiteMinder Federation Endpoint Guide for the additional endpoint requirements.