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
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) How to install the jTDS JDBC driver on WildFly for use with Data Collections in RSA Identity Governance & Lifecycle RSA Authentication Manager 8.8 Setup and Configuration Guide Artifacts to gather in RSA Identity Governance & Lifecycle
Don't see what you're looking for?
