Configure the active content filter for Activities, Communities, and Bookmarks

IBM Connections provides a set of active content filter (ACF) configuration files that we can apply to the Activities, Communities, or Bookmarks applications to limit or widen the types of content that users can add to their entries.

This is not a required procedure. Only perform this to change the level of filtering performed by the active content filter.

All of the applications, except Blogs, Wikis, and Forums, use the default acf-config.xml file, which filters active content in the following ways:

• We can change the formatting of content within rich text fields, but styles cannot be added to entries using HTML.

• Javascript is stripped from all entries.

• Flash animations are not permitted.

The following configuration files are shipped with Connections, and stored in the LotusConnections-config\extern directory. To change the level of filtering that is performed by the active content filter, we can replace the default configuration file with one of these files:

acf-config-nf.xml

Allow style changes, but strips forms and flash. The types of forms that are not allowed are form HTML elements. Form HTML elements are used to add things like buttons or fields to a web page.

acf-config-nf-ns.xml

Prevents style changes and strips forms and flash.

acf-config-nm.xml

Prevents users from changing the margins on images. By default, these applications permit image margin changes.

acf-config-ns.xml

Allow forms, but strips style changes and flash. Preventing style changes affects rich text fields. If we configure the active content filter to prevent style changes, then users will not be able to perform the common tasks associated with changing the style of rich text content, such as changing the font color, margins, and so on.

1. Edit LotusConnections-config.xml.

   1. Access the Connections configuration file: execfile("connectionsConfig.py")

      If we are prompted to specify a service to connect to, type 1 to select the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file by using a local file path, we must select the node where the file is stored. This information is not used by the wsadmin client when we are making configuration changes.

   2. Check out Connections configuration files:

      LCConfigService.checkOutConfig("/tmp","cell_name")

      where:

      • /tmp is the temporary working directory to which configuration files are copied. The files are kept in this working directory while you edit them.

        • With Windows, use a forward slash for the directory. For example: "/tmp".

      • To determine: print AdminControl.getCell()

   3. Edit LotusConnections-config.xml

   4. Find the <sloc:serviceReference> element for the application to which to change filtering levels. The application name is specified in the serviceName attribute.

      Change the active content filter configuration for the applications with the following serviceName attributes:

      • Activities
      • Communities
      • Bookmarks

   5. Add the following attribute to the <sloc:serviceReference> element for the application to change:

      For example:

      acf_config_file="file_name"

      where file_name is one of the configuration files (acf-config-nf.xml, acf-config-nf-ns.xml, acf-config-nm.xml, or acf-config-ns.xml).

      For example, to configure the Activities application to prevent image margin changes, you could add the following acf_config_file element:

      <sloc:serviceReference 
       bootstrapHost="myServer.myco.com" 
       bootstrapPort="2817" 
       clusterName="" 
       enabled="true" 
       serviceName="activities"  
       ssl_enabled="true" 
        acf_config_file="acf-config-nm.xml"> 
        <sloc:href>
          <sloc:hrefPathPrefix>/blogs</sloc:hrefPathPrefix>
          <sloc:static 
           href="http://enterprise.myco.com:9082" 
           ssl_href="https://enterprise.myco.com:9447"/>
          <sloc:interService href="https://enterprise.myco.com:9447"/>
        </sloc:href>
      </sloc:serviceReference>

   6. Repeat Steps d and e to apply different filtering levels to different applications, and then save and close the configuration file.

   7. After making changes, check the configuration file back in and we must do so during the same wsadmin session in which you checked them out for the changes to take effect. See Applying common configuration property changes for information about how to save and apply the changes.

2. Synchronize the nodes using the WAS console for the network deployment system.

3. Restart the WAS.

Parent topic:
Secure applications from malicious attack

Related:

Administer Communities

Administer Forums

Related:

Apply common configuration property changes

Related reference:

Common configuration properties