wif - Window Identity Foundation vs DotnetOpenAuth -


Can someone tell me the difference between the DotNet OpenOff and the Window Identity Foundation? And in these cases, one of these should be given priority.

Thanks in advance

WIF STS - Use for authentication with ADFS such as There is a group of .NET classes done. This enables the development of claim-based applications, that means the user receives a proof of properties from a stock of recognition within the SAML token and in the form of claims.

WIIF easily integrates an application from the cloud by example Azure Active Directory

DotNetOpenAuth is mainly used by NET classes for authorization (or consent) Have a group. The user authenticates somewhere (supports OpenID's Dotnet OpenAuth) and is asked if they give permission to send a set of features from the identity store on the application. If they agree that the application has passed the features in the JSON Token.

WIF works well in an enterprise environment where you want SSO in Microsoft Stack. CRM Dynamics, Office 365, Ezur, SharePoint use all claims-enabled paradigms.

DotNet works well with open-end applications, obviously some kind of user consent is required.


Comments