Allow per-connection contract configuration for WSFed

Idea ID 2782651

Allow per-connection contract configuration for WSFed

The WSFed connection interface only allows for contract assignment for the protocol, not on a per-connection basis like SAML2. For connections that require different authentication contracts, such as 2FA versus risk-based versus Kerberos, this negates the ability to select different contracts based on need.

In our case, we have both default 2FA and Risk-based 2FA available, but not all our WSFed connections need that so the default is Kerberos/WSFed. This prevents us from supporting 2FA WSFed for requesting customers like Sharepoint.
1 Comment
Micro Focus Contributor
Micro Focus Contributor
Shouldn't this go to Access Manager instead?
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.