Release Notes for AquaLogic Interaction Identity Service - LDAP 2.2
Contents
Version History
Release Notes Overview
Version 2.2 MP2
Supported Operating Systems, Application Servers, and Browsers
Supported BEA Products
Documentation
New Features
Issues Addressed
Known Issues
Version 2.2 MP1
Supported Operating Systems, Application Servers, and Browsers
Supported BEA Products
Documentation
New Features
Known Issues
Version 2.2
Supported Operating Systems, Application Servers, and Browsers
Supported BEA Products
Documentation
New Features
Issues Addressed
Known Issues
Version History

Version 2.2 MP2 - released April 2008

Version 2.2 MP1 - released April 2007

Version 2.2 - released October 2006

Release Notes Overview

These release notes cover all releases of AquaLogic Interaction Identity Service - LDAP 2.2, including hotfixes and maintenance packs. For information on a particular release, please go to the appropriate section of these release notes.

Release notes are occasionally updated after the release date. For the most up-to-date release notes, go to http://www.oracle.com/technology/documentation/index.html.

Version 2.2 MP2

Supported Operating Systems, Application Servers, Databases, and Browsers

Refer to the Interoperability page at one.bea.com/support for the latest information on supported operating systems, application servers, databases, and browsers.

At the time of release, AquaLogic Interaction Identity Service - LDAP 2.2 MP2 supports the following:

- Operating Systems: AIX 5.3 (on POWER3, POWER4, POWER5); HP-UX 11i V2 (on Itanium); RedHat Enterprise Linux 4 update 3 (on x86); Solaris 8, 9, and 10 (on SPARC); SUSE Enterprise Server 9 (on x86); Windows Server 2003 SP1 or R2 (on x86)
- LDAP Vendors: Novell eDirectory, Lotus Notes, and iPlanet/SunONE.

Supported BEA Products

Refer to the Interoperability page at one.bea.com/support for the latest information on supported BEA products.

At the time of release, AquaLogic Interaction Identity Service - LDAP 2.2 MP2 supports the following:

- BEA AquaLogic Interaction 6.5, 6.1, 6.1.0.1, 6.1 MP1

Documentation

The following product documentation is available for download from http://www.oracle.com/technology/documentation/index.html:

Document Title and File Name | Document Description
--- | ---
Installation and Upgrade Guide for AquaLogic Interaction Identity Service - LDAP 2.2 MP2 install.pdf | Describes how to install and upgrade the components of AquaLogic Interaction Identity Service - LDAP 2.2 MP2

Issues Addressed

- LDAP IDS throws too many service exception messages into the job log. (Issue 60646)

Known Issues

- In the Authentication Source wizard, if an attempt to save the LDAP template fails, this error is not reported to the user.
- Several AquaLogic User Interaction products can only handle headers less than 4KB in size by default. However, certain configurations of AquaLogic Interaction (Plumtree Foundation) may send headers that are greater than 4KB in size. This could occur by the portal passing large portlet preferences, third party headers, SSO tokens, etc. This will result in requests being dropped by affected products which could affect the functionality of that product. You may notice this as unexpected error messages being returned by the portal. You can also detect the size of the headers by using a TCP tracing tool such as Ethereal that can list header sizes. (Issue #48757)

  The products affected are:

  o AquaLogic Interaction Collaboration
  o AquaLogic Interaction Publisher
  o AquaLogic Interaction Studio
  o AquaLogic Interaction Analytics
  o AquaLogic Interaction Identity Service - LDAP
  o AquaLogic Interaction Content Service - Documentum
  o AquaLogic Interaction Portlet Suite - Lotus Notes
  o AquaLogic Interaction Portlet Suite - IMAP

  To resolve the issue for all of these products except Publisher, you must update the file plumtree-bootstrap.jar on all servers that are running the affected products. The steps are:

  1. Contact support and get a newer version of plumtree-bootstrap.jar.

  2. Place the file in the following common folder that is used by all products:

  > i. Windows: <install_folder>\common\container\tomcat\5.0.28\bin\

  > ii. Unix: <install_root>/common/container/tomcat/5.0.28/bin/

  3. Restart the services for all products running on that particular server.

  Replacing plumtree-bootstrap.jar here will update the all products running on that particular server and allow headers up to 16KB in size.

  To resolve the issue on Plumtree Publisher, you must edit the configuration on the server running Plumtree Publisher. The steps are:w

  1. Edit the file server.xml in the folder ptcs/6.2/container/deploy/jbossweb-tomcat50.sar/ and add the attribute maxHttpHeaderSize="8192" (or higher if necessary) to the HTTP/1.1 <Connector> element that appears at the beginning of the file.

  2. Restart the Publisher service

Version 2.2 MP1

Supported Operating Systems, Application Servers, Databases, and Browsers

Refer to the Interoperability page at one.bea.com/support for the latest information on supported operating systems, application servers, databases, and browsers.

At the time of release, AquaLogic Interaction Identity Service - LDAP 2.2 MP1 supports the following:

- Operating Systems: AIX 5.3 (on POWER3, POWER4, POWER5); HP-UX 11i V2 (on Itanium); RedHat Enterprise Linux 4 update 3 (on x86); Solaris 8, 9, and 10 (on SPARC); SUSE Enterprise Server 9 (on x86); Windows Server 2003 SP1 or R2 (on x86)
- LDAP Vendors: Novell eDirectory, Lotus Notes, and iPlanet/SunONE.

Supported BEA Products

Refer to the Interoperability page at one.bea.com/support for the latest information on supported BEA products.

At the time of release, AquaLogic Interaction Identity Service - LDAP 2.2 MP1 supports the following:

- BEA AquaLogic Interaction 6.1, 6.1.0.1, 6.1 MP1

Documentation

The following product documentation is available for download from http://www.oracle.com/technology/documentation/index.html:

Document Title and File Name | Document Description
--- | ---
Installation and Upgrade Guide for AquaLogic Interaction Identity Service - LDAP 2.2 MP1 install.pdf | Describes how to install and upgrade the components of AquaLogic Interaction Identity Service - LDAP v2.2 MP1

New Features

- The Plumtree Identity Service - LDAP has been rebranded to be the AquaLogic Interaction Identity Service - LDAP.
- AquaLogic Interaction Identity Service - LDAP now supports HP-UX.

Known Issues

- In the Authentication Source wizard, if an attempt to save the LDAP template fails, this error is not reported to the user.
- Several AquaLogic User Interaction products can only handle headers less than 4KB in size by default. However, certain configurations of AquaLogic Interaction (Plumtree Foundation) may send headers that are greater than 4KB in size. This could occur by the portal passing large portlet preferences, third party headers, SSO tokens, etc. This will result in requests being dropped by affected products which could affect the functionality of that product. You may notice this as unexpected error messages being returned by the portal. You can also detect the size of the headers by using a TCP tracing tool such as Ethereal that can list header sizes. (Issue #48757)

  The products affected are:

  o AquaLogic Interaction Collaboration
  o AquaLogic Interaction Publisher
  o AquaLogic Interaction Studio
  o AquaLogic Interaction Analytics
  o AquaLogic Interaction Identity Service - LDAP
  o AquaLogic Interaction Content Service - Documentum
  o AquaLogic Interaction Portlet Suite - Lotus Notes
  o AquaLogic Interaction Portlet Suite - IMAP

  To resolve the issue for all of these products except Publisher, you must update the file plumtree-bootstrap.jar on all servers that are running the affected products. The steps are:

  1. Contact support and get a newer version of plumtree-bootstrap.jar.

  2. Place the file in the following common folder that is used by all products:

  > i. Windows: <install_folder>\common\container\tomcat\5.0.28\bin\

  > ii. Unix: <install_root>/common/container/tomcat/5.0.28/bin/

  3. Restart the services for all products running on that particular server.

  Replacing plumtree-bootstrap.jar here will update the all products running on that particular server and allow headers up to 16KB in size.

  To resolve the issue on Plumtree Publisher, you must edit the configuration on the server running Plumtree Publisher. The steps are:w

  1. Edit the file server.xml in the folder ptcs/6.2/container/deploy/jbossweb-tomcat50.sar/ and add the attribute maxHttpHeaderSize="8192" (or higher if necessary) to the HTTP/1.1 <Connector> element that appears at the beginning of the file.

  2. Restart the Publisher service

Version 2.2

Supported Operating Systems, Application Servers, Databases, and Browsers

At the time of release, AquaLogic Interaction Identity Service - LDAP 2.2 supports the following:

- Operating Systems: Windows 2000 SP4, Windows 2003 Standard Edition, Solaris 8 and 9 on SPARC, and AIX 5.3 on POWER3, POWER4, POWER5.
- LDAP Vendors: Novell eDirectory, Lotus Notes, and iPlanet/SunONE.

Supported BEA Products

Refer to the Interoperability page in the Product Center at support.plumtree.com for the latest information on supported BEA products.

At the time of release, AquaLogic Interaction Identity Service – LDAP 2.2 supports the following:

- AquaLogic Interaction 6.1

Documentation

The following product documentation is available for download from http://www.oracle.com/technology/documentation/index.html:

Document Title and File Name | Document Description
--- | ---
Installation and Upgrade Guide for AquaLogic Interaction Identity Service – LDAP 2.2 install.pdf | Describes how to install and upgrade the components of AquaLogic Interaction Identity Service – LDAP v2.2

New Features

- The Plumtree Identity Service - LDAP has been rebranded to be the AquaLogic Interaction Identity Service - LDAP.

Known Issues

- In the Authentication Source wizard, if an attempt to save the LDAP template fails, this error is not reported to the user.
- Several AquaLogic User Interaction products can only handle headers less than 4KB in size by default. However, certain configurations of AquaLogic Interaction (Plumtree Foundation) may send headers that are greater than 4KB in size. This could occur by the portal passing large portlet preferences, third party headers, SSO tokens, etc. This will result in requests being dropped by affected products which could affect the functionality of that product. You may notice this as unexpected error messages being returned by the portal. You can also detect the size of the headers by using a TCP tracing tool such as Ethereal that can list header sizes. (Issue #48757)

  The products affected are:

  o AquaLogic Interaction Collaboration
  o AquaLogic Interaction Publisher
  o AquaLogic Interaction Studio
  o AquaLogic Interaction Analytics
  o AquaLogic Interaction Identity Service - LDAP
  o AquaLogic Interaction Content Service - Documentum
  o AquaLogic Interaction Portlet Suite - Lotus Notes
  o AquaLogic Interaction Portlet Suite - IMAP

  To resolve the issue for all of these products except Publisher, you must update the file plumtree-bootstrap.jar on all servers that are running the affected products. The steps are:

  1. Contact support and get a newer version of plumtree-bootstrap.jar.

  2. Place the file in the following common folder that is used by all products:

  > i. Windows: <install_folder>\common\container\tomcat\5.0.28\bin\

  > ii. Unix: <install_root>/common/container/tomcat/5.0.28/bin/

  3. Restart the services for all products running on that particular server.

  Replacing plumtree-bootstrap.jar here will update the all products running on that particular server and allow headers up to 16KB in size.

  To resolve the issue on Plumtree Publisher, you must edit the configuration on the server running Plumtree Publisher. The steps are:w

  1. Edit the file server.xml in the folder ptcs/6.2/container/deploy/jbossweb-tomcat50.sar/ and add the attribute maxHttpHeaderSize="8192" (or higher if necessary) to the HTTP/1.1 <Connector> element that appears at the beginning of the file.

  2. Restart the Publisher service.