Error: 'No Relying Party configured or enabled that can be identified by principal' in RSA Federated Identity Manager (FIM)
Originally Published: 2005-09-13
Article Number
Applies To
Microsoft Windows 2000 SP4
Issue
The following error appears in web browser:
Error 500 - Internal Server Error
The server encountered the following unexpected condition: Error in RSA Federated Identity Manager: Error encountered in Relying Party servlet: com.rsa.csf.common.exceptionbase.CsfApplicationException: Error in Relying Party while processing Asserting Party response: ;
nested exception is: com.rsa.csf.techservice.saml.opensaml.SAMLException: SAML Requester error: No Relying Party configured or enabled that can be identified by principal "samlrequestcaller5"
Cause
Resolution
Related Articles
RSA Identity Governance and Lifecyle users who do not belong to role can not be identified Number of Views CERT/CC Vulnerability Note VU#475445: Potential Impact on RSA Products Number of Views Apache vulnerability 'Apache HTTP Server mod_rewrite' from scan Number of Views Apache Struts 2 Freemarker Remote Code Execution Vulnerability (CVE-2017-12611) in RSA Products Number of Views RSA SecurID Access identity router will not start after reboot on Microsoft Hyper-V Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager 8.9 Release Notes (January 2026) Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU Disabling weak ciphers using port 1813 in RSA Authentication Manager 8.3 patch 1
Don't see what you're looking for?
