OAuthWebSecurity迁移从了OpenID 2.0至OpenID连接

问题描述

谷歌早些时候曾宣布了OpenID 2.0的德precation停药并在四月2015年不幸的是，大多数人都和我一样，我们现有的应用程序已经有C $ CS一堆$使用被写入基于这种业务的 OAuthWebSecurity 从 DotNetOpenAuth的NuGet包。

是否有更新，这种变化对这个的NuGet包，这将有助于迁移到这个新的更新，而不是通过搜索替代品，如OWIN放弃我所有过去的努力在http://www.asp.net/mvc/overview/security/create-an-aspnet-mvc-5-app-with-facebook-and-google-oauth2-and-openid-sign-on

其次，有一种可能性，即其他平台如 Facebook，微博，LinkedIn 也将放弃OpenID的2.0呢？

  OAuthWebSecurity.RequestAuthentication（谷歌，HREF（〜/帐号/ RegisterService，新的{} RETURNURL））;
 

解决方案

有关新闻DotNetOpenAuth你要问这个项目的维护者。他们是唯一的洞察未来的发展。

的Facebook，Twitter和LinkedIn不要使用OpenID的。 Twitter的使​​用OAuth 1.0，而Facebook和LinkedIn使用OAuth 2.由于这个答案的写作，他们都没有宣布，计划从目前的认证标准移开。

Google had earlier announced the deprecation and discontinuation of openID 2.0 on April 2015. Unfortunately for most people like me, our existing applications already have a bunch of codes written based on this service using OAuthWebSecurity from DotNetOpenAuth nuget package.

Is there an update to this change on this nuget package that will assist to migrate to this new update rather than abandoning all my past efforts by searching for alternatives such as OWIN as explained in http://www.asp.net/mvc/overview/security/create-an-aspnet-mvc-5-app-with-facebook-and-google-oauth2-and-openid-sign-on

Secondly, is there a possibility that other platforms such as Facebook, Twitter, LinkedIn will also abandon OpenID 2.0 as well?

OAuthWebSecurity.RequestAuthentication("google", Href("~/Account/RegisterService", new { returnUrl }));

解决方案

For news about DotNetOpenAuth you will have to ask the maintainers of the project. They are the only ones with insight into future development.

Facebook, Twitter, and LinkedIn don't use OpenID. Twitter uses OAuth 1.0 while Facebook and LinkedIn use OAuth 2. As of the writing of this answer, none of them have announced plans to move away from their current authentication standards.

这篇关于OAuthWebSecurity迁移从了OpenID 2.0至OpenID连接的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！