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
Error: 'No Relying Party configured or enabled that can be identified by principal 'samlrequestcaller'' in RSA Federated I… Number of Views Root Cause Identified for the SecurID 3.0 App Token Import Issue Number of Views 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 Identifying Custom Attribute column name in RSA Governance & Lifecycle Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide How to Download OTP Token Seed Files from myRSA RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?
