Previous Topic: Known Issues for Legacy FederationNext Topic: Federation Defects Fixed in 12.51


Known Issues for Partnership Federation

Metadata File Name is Incorrect During Metadata Export (172063)

Symptom:

For a Administrative UI using Internet Explorer 9, exporting metadata for a federation entity results in an incorrect file name that you cannot open or download.

When you export metadata at the entity level, a window opens and displays the information to be exported. After you review the information and click Export, a dialog at the bottom of the screen opens, asking to open or save the file. For example:

Do you want to open or save LocalIdPMetadata.xml from exampleserver01? 

Instead of using a proper metadata filename, it uses the name FileDownload. You cannot download the file with this name.

Solution:

For Internet Explorer 9, verify that the browser setting “Do not save encrypted pages to disk” is unchecked before exporting entity metadata. To download the metadata file successfully, this option must be disabled. The setting is in Tools, Internet Options, Advanced tab, under the Security section.

Consistent Use of CONSUMERID or NAME in an Intersite Transfer URL Required (169724)

Symptom:

At the SAML 1.1 producer, links that represent URLs to the intersite transfer service initiate single sign-on. The CONSUMERID or the NAME query parameter is required in the URL.

If you change the query parameter in a URL from one request to another, an error can occur.

Solution:

Select the CONSUMERID or the NAME query parameter for all intersite transfer URLs. Do not interchange these parameters from request to request.

This limitation applies only to SAML 1.1 Producer-to-Consumer partnerships.

WSFED RP Entity with SAML 2.0 Token Type Not Supported (167916)

The Administrative UI lets you configure a CA SiteMinder® local WSFED RP entity with a SAML 2.0 token type. However, when you create a WSFED RP-to-IP partnership, you cannot select this RP entity then proceed with the partnership configuration.

The WSFED RP-to-IP partnership does not support the RP entity with the SAML 2.0 token type.