Home

 

Disabling support for flash animations

If you have enabled the active content filter in Lotus Connections, its default behavior is to allow flash animations to be displayed in an IFRAME in Blogs and Wikis after filtering out any malicious parameters that are found in the embedded object description. Displaying the animation in an IFRAME limits the amount of page data the animation can access. You can disable this support if you prefer.

If you disable support for flash animations, then when a person tries to add an embedded flash animation file to a wiki or blog entry, it will be removed by the active content filter and will not appear on the page. This procedure does not remove flash animation files that users have already added to their blogs nor does it prevent them from being displayed. You must explicitly remove or ask the entry owners to remove the flash animation files from existing entries.

To edit configuration files, use the wsadmin client. See Start wsadmin for details.


To disable support for flash animations...

  1. Use wsadmin to access and check out the Lotus Connections configuration files.

    1. Access the Lotus Connections configuration file:

      • Stand-alone deployment: execfile("connectionsConfig.py")

      • Network deployment: execfile("WAS_HOME/profiles/Dmgr01/config/bin_lc_admin/connectionsConfig.py")If you are prompted to specify which server to connect to, type 1.

        This information is not used by wsadmin when you are making configuration changes.

    2. Check out the Lotus Connections configuration files...

      LCConfigService.checkOutConfig("<working_directory>","cell_name") where:

      • <working_directory> is the temporary working directory to which the configuration XML and XSD files are copied and are stored while you make changes to them. Use forward slashes to separate directories in the file path, even if you are using the Microsoft Windows operating system.

      • cell_name is the name of the WebSphere Application Server cell hosting the Lotus Connections feature. This argument is required even in stand-alone deployments. This argument is also case-sensitive, so type it with care. If you do not know the cell name, do one of the following to determine it:

        • Stand-alone deployment: From the file system... 

            WAS_HOME\profiles\profile_name\config\cells\

      • Network deployment: From wsadmin... 

          print AdminControl.getCell()

      For example:

      • AIX/Linux: 

          LCConfigService.checkOutConfig("/opt/temp","foo01Cell01")

    3. Microsoft Windows: 

        LCConfigService.checkOutConfig("c:/temp","foo01Cell01")

  2. Set the value of the allowedContent.contentType.enabled parameter to false... 

      LCConfigService.updateConfig("allowedContent.contentType.enabled","false")

  3. After making changes, check the configuration files back in and 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 your changes.


Securing features from malicious attack

+

Search Tips   |   Advanced Search