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 RSA Identity Governance and Lifecyle users who do not belong to role can not be identified 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 RSA Governance & Lifecycle Recipes: Risk Analytics Dashboard Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager Patch Updates Downloading RSA Authentication Manager license files or RSA Software token seed records How to manage RSA Authentication Manager console and virtual host certificates with keytool
Don't see what you're looking for?
