Release Notes › Federation Release Notes › Known Issues for Legacy Federation

Known Issues for Legacy Federation

This section contains the following topics:

Attributes Appear Truncated at the Relying Party (157913)

Unable to View Legacy Federation Objects in the UI (119335)

Filtered Packages for JBoss Container Require Changes (168893)

Attributes Appear Truncated at the Relying Party (157913)

Symptom:

The following issues occur:

• The directory attributes appear truncated at the relying party.
• The following message appears in the smtracedefault.log file:

  [WARNING: Response attribute will be trimmed. [attr = SMUSERGRP:memberOf] [actual attr len = number] [ response attr len = number]]
  

  Note: In the Warning message, SMUSERGRP represents the variable name and memberOf represents the attribute value. The error message is specific to your configuration.

Solution:

The maximum length for the user assertion attributes is configurable by modifying settings in the EntitlementGenerator.properties file. To modify the length, go to the CA SiteMinder Federation: Legacy Federation Guide and follow the procedure in the section "Specify the Maximum Length of Assertion Attributes."

Unable to View Legacy Federation Objects in the UI (119335)

Symptom:

After configuring legacy federation objects using the Policy Server Management API or the FSS Administrative UI and then upgrading to the CA SiteMinder® 12.52 Administrative UI, the legacy federation objects are not visible in the Administrative UI. When you try selecting a legacy federation object in the Administrative UI you see the message,

Error: [General]  The value for "Enabled" failed to convert to correct type.

Solution:

Run the XPS sweeper utility to help ensure the legacy federation objects build correctly. For information about the XPS sweeper utility, see the CA SiteMinder® Upgrade Guide.

Filtered Packages for JBoss Container Require Changes (168893)

Symptom:

The JBOSS container version 5.1 requires changes to the filtered packages specifications.

Solution:

1. Install the JBoss container.
2. Navigate to the following folder: JBoss_home/server/default/deployers/jbossweb.deployer/META-INF.
3. Open the war-deployers-jboss-beans.xml file.
4. Change the filteredPackages property:

   From:

   <property name="filteredPackages">javax.servlet,org.apache.commons.logging,javax.xml.parsers,org.xml.sax,org.w3c.dom</property>

   To:

   <property name="filteredPackages">javax.xml.namespace,org.apache.xml.resolver.helpers,javax.servlet,org.apache.commons.logging,javax.xml.parsers,org.xml.sax,org.w3c.dom</property>

5. Repeat the preceding step for the other entry of filteredPackages in the same file. Overall, there are two entries.
6. Save the file.

Continue with other configuration steps of affwebservices deployment.