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 Number of Views RSA Authentication Manager Glossary 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
Artifacts to gather in RSA Identity Governance & Lifecycle How to Update the Root (Server) and Client Certificates in RSA Identity Governance & Lifecycle How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle How to Download and Reinstall the AFX Server Archive in RSA Governance & Lifecycle
Don't see what you're looking for?
