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
RSA Ready Partner Program Number of Views RSA Governance & Lifecycle Partner Summary: Herjavec Group (Previously Securience) Number of Views RSA Governance & Lifecycle Partner Summary: Elementity 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 Details on RSA SecurID tokens and RSA Authentication Manager licenses Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA Authentication Manager Patch Updates RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to Download OTP Token Seed Files from myRSA
Don't see what you're looking for?
