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 RSA Governance & Lifecycle Recipes: Risk Analytics Dashboard Number of Views Network configuration lost after RSA Authentication Manager 8.7 SP1 upgrade on Azure Number of Views Email triggered for 'Please reset your current password' after a password reset Number of Views RSA Authentication Manager response to log4j vulnerabilities; CVE-2021-44228, CVE-2021-45046, CVE-2021-4104, CVE-2022-2330… Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…
Don't see what you're looking for?
