Sun OpenSSO Enterprise Policy Agent 3.0 Guide for IBM WebSphere Application Server 6.1/7.0 and WebSphere Portal Server 6.1

Adding the Agent Filter to the WebSphere Portal Server 6.1 Application

This required task integrates the WebSphere Portal Server 6.1 instance with the OpenSSO Enterprise environment.

Note: Perform this task only once per WebSphere Portal Server 6.1 instance for a given host.

The WebSphere Application Server/Portal Server agent provides a servlet filter that you can add to the WebSphere Portal Server 6.1 application. This filter allows the enforcement of coarse grained URL policies defined within OpenSSO Enterprise server to further control the access to protected resources on the WebSphere Portal Server 6.1 instance. The filter can also be configured to provide additional personalization information in the form of HTTP headers, cookies, or HTTP request attributes that can be used to further enhance the functionality of the protected components.

ProcedureTo Add the Agent Filter to the WebSphere Portal Server 6.1 Application

  1. Ensure that the WebSphere Portal Server 6.1 environment is down.

  2. Locate the wps.war/WEB-INF/web.xml file, which contains the deployment descriptors for WebSphere Portal Server 6.1.

    WebSphere Application Server can read this file at runtime from either of the following directories:

    • WAS-base/wp_profile/installedApps/Cell-Name/wps.ear/wps.war/WEB-INF

    • WAS-base/wp_profile/config/cells/Cell-Name/applications/wps.ear/deployments/wps/wps.war/WEB-INF

    where:

    • WAS-base represents the directory where WebSphere Portal Server 6.1 was installed

    • Cell-Name represents the WebSphere Portal Server 6.1 cell protected by the agent. The default is hostname.

  3. Backup the two web.xml files before modifying the deployment descriptors.

    Since you will modify the deployment descriptor in the next step, creating backup files is important, especially if you need to uninstall the agent in the future.

  4. Edit both web.xml files from the previous step, as follows:

    <display-name>WebSphere Portal Server</display-name>
    
    <filter id="Filter_PolicyAgent">
    <filter-name>Policy Agent</filter-name>
    <filter-class>
      com.sun.identity.agents.filter.AmAgentFilter
    </filter-class>
    </filter>
    
    ... //other filter definitions
    
    <filter-mapping id="FilterMapping_PolicyAgent">
      <filter-name>Policy Agent</filter-name>
      <url-pattern>/*</url-pattern>
    </filter-mapping>
    
    ... //other filter mappings
    
    </web-app>