Error: 'No Relying Party configured or enabled that can be identified by principal' 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 "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 Modify the RSA SecurID Access Prime Self-Service Portal (SSP) or Help Desk Admin Portal (HDAP) session timeout value Number of Views Change the maximum emergency passcode lifetime assigned by an RSA Authentication Manager Prime Kit Help Desk Admin Portal … Number of Views Help Desk Admin Portal random timeouts during admin login or when searching for a user in RSA Authentication Manager 8.1 Number of Views RSA Authentication Manager Prime Help Desk Admin (HDAP) and/or Self-Service Portal (SSP) not accessible after upgrade to R… 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?
