FIM- Editing Partner Entity Shows Wrong Protocol
Originally Published: 2010-02-19
Article Number
Applies To
fimconfig
Issue
When editing an existing partner entity in the FIM management console it always defaults to SAML 1.1. This happens even when the saved entity is SAML 2.0 or WSFED. This causes users to accidentally save a SAML 1.1 role to a SAML 2.0 partner.
Resolution
Related Articles
Ping Identity PingFederate 9.3 - Configure Bridge between RSA SecurID Access SAML IdP and Partner Service Providers Config… Number of Views RSA Ready Partner Program Number of Views RSA Governance & Lifecycle Partner Summary: Elementity Number of Views RSA Governance & Lifecycle Partner Summary: Herjavec Group (Previously Securience) Number of Views How to remove a decommissioned partner device from the Partners list on the RSA Data Loss Prevention Enterprise Manager GUI Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x
Don't see what you're looking for?
