Symptom:
CA SiteMinder® Federation was not accepting and processing the Assertion Consumer Service URL in the incoming authentication request. The system did not verify whether the authentication request had an Assertion Consumer Service URL defined.
Solution:
For an IdP-to-SP partnership, the Administrative UI has a new check box labeled Accept ACS URL in the Authnrequest. This check box is in the SSO section of the SSO and SLO step of the partnership configuration. To confirm that the URL is present and valid in the authentication request, and it is in the metadata, select this option.
STAR issue: 21361990
Symptom:
The -decryptionkeyalias command option was missing from the list of smfedexport command options.
Solution:
The -decryptionkeyalias command option is now in the table of command options.
STAR issue: 21594883-01
Symptom:
Policy server (FIPS only) threw the following exception while searching for IDP information for an SP-initiated request:
Exception while attempting to retrieve passwords:
java.lang.SecurityException: class "com.netegrity.util.ct"'s signer information does not match signer information of other classes in the same package.
Solution:
This issue has been corrected.
Star issue 21530627-01.
Symptom:
WS-FED Assertion Generation GetUserProp() function was causing a Policy Server failure.
Solution:
This issue is no longer a problem..
Star issue 21505894.
Symptom:
The user encountered the error "ACS_BAD_SAMLRESPONSE_XML" while running federation partnership in Siteminder FSS 12.51.
Solution:
CA SiteMinder® Federation is no longer shipping dom.jar and sax.jar file, which were causing the problem.
Star issue 21478695-1
The following updates were made to the Web Agent Option Pack Guide:
STAR issue: 21429459
Symptom:
In an indexed list of Assertion Consumer Service URLs, CA SiteMinder® Federation generated the assertion with the first entry in the list as the Recipient. The Recipient is required to match the index number.
Solution:
This issue is no longer a problem.
Star issues 21423322;1+21287493;1
Symptom:
SAML SSO was failing with "Could not parse SAML
response. Error message: null" as well as "ACS_BAD_SAMLRESPONSE_XML".
Solution:
This issue is no longer a problem.
Star issue 21313265;1.
Copyright © 2014 CA.
All rights reserved.
|
|