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
Last Modified: 2023-10-06
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 RSA Identity Governance and Lifecyle users who do not belong to role can not be identified Number of Views Unification fails to identify terminated or deleted users in RSA Identity Governance & Lifecycle Number of Views Want to encrypt without getting Base64 encoded result Number of Views Hyper-V DVD/CD or ISO Image Mounting Guidelines Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?
