RSA Federated Identity Manager (FIM) 2.5
RSA Federated Identity Manager (FIM) 2.6
What can cause: SAMLException: No assertion associated with artifact
FIM is the AP in this scenario with an unknown RP
In the FIM debug.log:
2006-09-16 21:29:52,193 FATAL - exception:
com.rsa.csf.techservice.saml.opensaml.SAMLException: No assertion associated with artifact
at com.rsa.csf.clientservice.saml.SamlRequestProcessorServiceBean.retrieveAssertionsByArtifact(Lcom.rsa.csf.techservice.saml.table.SamlAssertionTableProxy;Lcom.rsa.csf.techservice.saml.signature.XMLSecurityProvider;[Lcom.rsa.csf.techservice.saml.opensaml.SAMLAssertionArtifact;)[Lcom.rsa.csf.techservice.saml.opensaml.SAMLAssertion;(Unknown Source)
This message can be caused when the RP receives back a different assertion ID then what was sent by the AP
Request for the same artifact a second time by the RP will also cause this error
Look at the code on the RP side to determine if the RP is requesting the same artifact twice. If it is RSA FIM, put the FIM server in debug mode.
By using the FIM debug.log log, you can compare what the assertion ID is sent and what assertion ID the RP is processing.
|Legacy Article ID||a32114|