Error: 'No Relying Party configured or enabled that can be identified by principal 'samlrequestcaller'' 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 'samlrequestcaller'
Cause
This error indicates that the configuration for identifying the RP over the SOAP channel contains a mismatch. In this case, HTTP Basic Authentication is configured to identify which RP is sending a request over the SOAP channel.
Resolution
Related Articles
Error: 'No Relying Party configured or enabled that can be identified by principal' in RSA Federated Identity Manager (FIM) Number of Views FortiGate Firewall - Configure RADIUS Authentication Manager Using Admin Access UI - RSA Ready Implementation Guide Number of Views FortiGate Firewall - SAML My Page SSO Configuration Using Admin Access UI - RSA Ready Implementation Guide Number of Views FortiGate Firewall - RADIUS Configuration Using Admin Access UI - RSA Ready Implementation Guide Number of Views Scheduled clean up job does not run but manual clean up works on Authentication Manager 8.x Number of Views
Trending Articles
RSA Authentication Manager 8.7 SP1 Patch 1 Hotfix 1 RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager 8.9 Setup and Configuration Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?
