FIM- Editing Partner Entity Shows Wrong Protocol
Originally Published: 2010-02-19
Last Modified: 2023-10-06
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
RSA Ready Partner Program 51Number of Views RSA Authentication Manager Glossary 10Number of Views How to remove a decommissioned partner device from the Partners list on the RSA Data Loss Prevention Enterprise Manager GUI 26Number of Views RSA Governance & Lifecycle Partner Summary: Elementity 32Number of Views RSA Governance & Lifecycle Partner Summary: Herjavec Group (Previously Securience) 30Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?