blocks|key|160972|text|我花了几个小时才弄明白，但问题是@CrazyCoder提到的CallbackPath。我意识到public+void+ConfigureAuth(IAppBuilder+app)+中的CallbackPath必须与在ChallengeResult中设置的不同。如果它们相同，就会在OWIN中抛出一个500错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|BOLD|entityRanges|data|160973|我为ConfigureAuth(IAppBuilder+app)编写的代码是|160974|var+googleOptions+=+new+Microsoft.Owin.Security.Google.GoogleOAuth2AuthenticationOptions
{
++++ClientId+=+"xxx",
++++ClientSecret+=+"yyy",
++++CallbackPath+=+new+PathString("/callbacks/google"),+//this+is+never+called+by+MVC,+but+needs+to+be+registered+at+your+oAuth+provider

++++Provider+=+new+GoogleOAuth2AuthenticationProvider
++++{
++++++++OnAuthenticated+=+(context)+=>
++++++++{
++++++++++++context.Identity.AddClaim(new+Claim("picture",+context.User.GetValue("picture").ToString()));
++++++++++++context.Identity.AddClaim(new+Claim("profile",+context.User.GetValue("profile").ToString()));
++++++++++++return+Task.FromResult(0);
++++++++}++++++
++++}
};

googleOptions.Scope.Add("email");

app.UseGoogleAuthentication(googleOptions);|code-block|syntax|javascript|160975|我的“回调”控制器代码是：|160976|//+GET:+/callbacks/googlereturn+-+callback+Action
[AllowAnonymous]
public+async+Task<ActionResult>+googlereturn()
{
++++++++return+View();
}

//POST:+/Account/GooglePlus
public+ActionResult+GooglePlus()
{
++++return+new+ChallengeResult("Google",+Request.Url.GetLeftPart(UriPartial.Authority)+%2B+"/callbacks/googlereturn",+null);++
++++//Needs+to+be+a+path+to+an+Action+that+will+handle+the+oAuth+Provider+callback
}

private+class+ChallengeResult+:+HttpUnauthorizedResult
{
++++public+ChallengeResult(string+provider,+string+redirectUri)
++++++++:+this(provider,+redirectUri,+null)
++++{
++++}

++++public+ChallengeResult(string+provider,+string+redirectUri,+string+userId)
++++{
++++++++LoginProvider+=+provider;
++++++++RedirectUri+=+redirectUri;
++++++++UserId+=+userId;
++++}

++++public+string+LoginProvider+{+get;+set;+}
++++public+string+RedirectUri+{+get;+set;+}
++++public+string+UserId+{+get;+set;+}

++++public+override+void+ExecuteResult(ControllerContext+context)
++++{
++++++++var+properties+=+new+AuthenticationProperties()+{+RedirectUri+=+RedirectUri+};
++++++++if+(UserId+!=+null)
++++++++{
++++++++++++properties.Dictionary[XsrfKey]+=+UserId;
++++++++}
++++++++context.HttpContext.GetOwinContext().Authentication.Challenge(properties,+LoginProvider);
++++}
}|160977|160978|callbacks/google似乎由OWIN|unordered-list-item|160979|callbacks/googlereturn处理似乎由MVC|160980|处理|160981|现在一切都正常了，尽管我很想知道到底发生了什么|160982|我的建议是，除非你有其他要求，否则让OWIN使用默认的重定向路径，并确保你自己不会使用它们。|160983|entityMap^0|U|C|1B|16|2K|C|30|F|2I|1T|0|0|12|2|U|0|0|0|D|0|0|0|0|N|0|0|U|0|0|2|0|0|N|0|0|1A|0^^$0|@$1|2|3|4|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]|$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]|$9|1E|A|1F|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|1G|8|@$9|1H|A|1I|B|D]|$9|1J|A|1K|B|C]]|E|@]|F|$]]|$1|I|3|J|5|K|7|1L|8|@]|E|@]|F|$L|M]]|$1|N|3|O|5|6|7|1M|8|@$9|1N|A|1O|B|D]]|E|@]|F|$]]|$1|P|3|Q|5|K|7|1P|8|@]|E|@]|F|$L|M]]|$1|R|3|-4|5|6|7|1Q|8|@]|E|@]|F|$]]|$1|S|3|T|5|U|7|1R|8|@$9|1S|A|1T|B|D]]|E|@]|F|$]]|$1|V|3|W|5|U|7|1U|8|@$9|1V|A|1W|B|D]]|E|@]|F|$]]|$1|X|3|Y|5|6|7|1X|8|@$9|1Y|A|1Z|B|D]]|E|@]|F|$]]|$1|Z|3|10|5|6|7|20|8|@$9|21|A|22|B|D]]|E|@]|F|$]]|$1|11|3|12|5|6|7|23|8|@$9|24|A|25|B|D]]|E|@]|F|$]]|$1|13|3|-4|5|6|7|26|8|@]|E|@]|F|$]]]|14|$]]

This took me hours to figure out, but the issue is the <code>CallbackPath</code> as mentioned by @CrazyCoder. I realised that the <code>CallbackPath</code> in <code>public void ConfigureAuth(IAppBuilder app)</code> MUST be different to when it is being set in the <code>ChallengeResult</code>. If they are the same a 500 error is thrown in OWIN.

My code is for <code>ConfigureAuth(IAppBuilder app)</code> is

<pre><code>var googleOptions = new Microsoft.Owin.Security.Google.GoogleOAuth2AuthenticationOptions
{
 ClientId = "xxx",
 ClientSecret = "yyy",
 CallbackPath = new PathString("/callbacks/google"), //this is never called by MVC, but needs to be registered at your oAuth provider

 Provider = new GoogleOAuth2AuthenticationProvider
 {
 OnAuthenticated = (context) =&gt;
 {
 context.Identity.AddClaim(new Claim("picture", context.User.GetValue("picture").ToString()));
 context.Identity.AddClaim(new Claim("profile", context.User.GetValue("profile").ToString()));
 return Task.FromResult(0);
 } 
 }
};

googleOptions.Scope.Add("email");

app.UseGoogleAuthentication(googleOptions);
</code></pre>

My 'callbacks' Controller code is:

<pre><code>// GET: /callbacks/googlereturn - callback Action
[AllowAnonymous]
public async Task&lt;ActionResult&gt; googlereturn()
{
 return View();
}

//POST: /Account/GooglePlus
public ActionResult GooglePlus()
{
 return new ChallengeResult("Google", Request.Url.GetLeftPart(UriPartial.Authority) + "/callbacks/googlereturn", null); 
 //Needs to be a path to an Action that will handle the oAuth Provider callback
}

private class ChallengeResult : HttpUnauthorizedResult
{
 public ChallengeResult(string provider, string redirectUri)
 : this(provider, redirectUri, null)
 {
 }

 public ChallengeResult(string provider, string redirectUri, string userId)
 {
 LoginProvider = provider;
 RedirectUri = redirectUri;
 UserId = userId;
 }

 public string LoginProvider { get; set; }
 public string RedirectUri { get; set; }
 public string UserId { get; set; }

 public override void ExecuteResult(ControllerContext context)
 {
 var properties = new AuthenticationProperties() { RedirectUri = RedirectUri };
 if (UserId != null)
 {
 properties.Dictionary[XsrfKey] = UserId;
 }
 context.HttpContext.GetOwinContext().Authentication.Challenge(properties, LoginProvider);
 }
}
</code></pre>

<ul>
<li>callbacks/google seems to handled by OWIN</li>
<li>callbacks/googlereturn seems to handled by MVC</li>
</ul>

It is all working now, although would love to know exactly what is happening 'under the bonnet'

My advice, unless you have another requirement, is to let OWIN use default redirect paths and make sure you don't use them yourself.

blocks|key|160991|text|为了简单起见，我使用默认的带有身份验证的ASP.NET+MVC5模板，但希望这个模板可以针对不同的用例进行修改。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|160992|StartupAuth.cs|offset|length|style|BOLD|160993|请勿自定义重定向路径。它被/signin-google所取代，而我试图绕过它的尝试导致了“静默”(不在调试器中)内部服务器500错误。|160994|app.UseGoogleAuthentication(new+GoogleOAuth2AuthenticationOptions()
{
++++ClientId+=+"whatevs.apps.googleusercontent.com",
++++ClientSecret+=+"whatevs_secrut",
++++Provider+=+new+GoogleOAuth2AuthenticationProvider()
});|code-block|syntax|javascript|160995|确保将http://whatever.com/signin-google添加到https://console.developers.google.com/的APIs+&+auth+>+Credentials+>+Redirect+URIs部分中。|CODE|160996|RouteConfig.cs|160997|将一个路由添加到永久重定向控制器操作到您的路由。永久重定向是唯一可以满足这一要求的东西。仅仅直接指向回调URL是不够的。|160998|public+static+void+RegisterRoutes(RouteCollection+routes)
{
++++routes.IgnoreRoute("{resource}.axd/{*pathInfo}");

++++routes.MapRoute(
++++++++name:+"Google+API+Sign-in",
++++++++url:+"signin-google",
++++++++defaults:+new+{+controller+=+"Account",+action+=+"ExternalLoginCallbackRedirect"+}
++++);

++++routes.MapRoute(
++++++++name:+"Default",
++++++++url:+"{controller}/{action}/{id}",
++++++++defaults:+new+{+controller+=+"Home",+action+=+"Index",+id+=+UrlParameter.Optional+}
++++);
}|160999|AccountController.cs|161000|永久重定向到内置的回调方法，这样就没问题了。|161001|[AllowAnonymous]
public+ActionResult+ExternalLoginCallbackRedirect(string+returnUrl)
{
++++return+RedirectPermanent("/Account/ExternalLoginCallback");
}|161002|已经在GitHub上发布了一个模板项目以供参考：https://github.com/Pritchard/Test-AspNetGoogleOAuth2Authentication|161003|entityMap|0|LINK|mutability|MUTABLE|url|http://whatever.com/signin-google|1|https://console.developers.google.com/|2|https://github.com/Pritchard/Test-AspNetGoogleOAuth2Authentication^0|0|0|E|0|0|0|26|B|2K|B|2Y|D|3|X|0|13|12|1|0|0|E|0|0|0|0|K|0|0|0|O|1U|2|0^^$0|@$1|2|3|4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1I|8|@$D|1J|E|1K|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1L|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1M|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|1N|8|@$D|1O|E|1P|F|Q]|$D|1Q|E|1R|F|Q]|$D|1S|E|1T|F|Q]]|9|@$D|1U|E|1V|1|1W]|$D|1X|E|1Y|1|1Z]]|A|$]]|$1|R|3|S|5|6|7|20|8|@$D|21|E|22|F|G]]|9|@]|A|$]]|$1|T|3|U|5|6|7|23|8|@]|9|@]|A|$]]|$1|V|3|W|5|L|7|24|8|@]|9|@]|A|$M|N]]|$1|X|3|Y|5|6|7|25|8|@$D|26|E|27|F|G]]|9|@]|A|$]]|$1|Z|3|10|5|6|7|28|8|@]|9|@]|A|$]]|$1|11|3|12|5|L|7|29|8|@]|9|@]|A|$M|N]]|$1|13|3|14|5|6|7|2A|8|@]|9|@$D|2B|E|2C|1|2D]]|A|$]]|$1|15|3|-4|5|6|7|2E|8|@]|9|@]|A|$]]]|16|$17|$5|18|19|1A|A|$1B|1C]]|1D|$5|18|19|1A|A|$1B|1E]]|1F|$5|18|19|1A|A|$1B|1G]]]]

I'm using the default ASP.NET MVC 5 template with Identity Authentication for simplicity, but hopefully this can be modified for different use cases.

StartupAuth.cs

Do not customize the redirect path. It gets replaced by /signin-google anyways and my attempts at getting around that caused "silent" (not in the debugger) Internal Server 500 errors.

<pre><code>app.UseGoogleAuthentication(new GoogleOAuth2AuthenticationOptions()
{
 ClientId = "whatevs.apps.googleusercontent.com",
 ClientSecret = "whatevs_secrut",
 Provider = new GoogleOAuth2AuthenticationProvider()
});
</code></pre>

Make sure to add <a href="http://whatever.com/signin-google" rel="nofollow">http://whatever.com/signin-google</a> to <a href="https://console.developers.google.com/" rel="nofollow">https://console.developers.google.com/</a> in your <code>APIs &amp; auth</code> > <code>Credentials</code> > <code>Redirect URIs</code> section.

RouteConfig.cs

Add a route to a permanent redirect controller action to your routes. Permanent redirects are the only thing that will suffice here. It is not enough to simply direct directly to the Callback URL.

<pre><code>public static void RegisterRoutes(RouteCollection routes)
{
 routes.IgnoreRoute("{resource}.axd/{*pathInfo}");

 routes.MapRoute(
 name: "Google API Sign-in",
 url: "signin-google",
 defaults: new { controller = "Account", action = "ExternalLoginCallbackRedirect" }
 );

 routes.MapRoute(
 name: "Default",
 url: "{controller}/{action}/{id}",
 defaults: new { controller = "Home", action = "Index", id = UrlParameter.Optional }
 );
}
</code></pre>

AccountController.cs

Permanent redirect to the built-in callback method and you should be fine.

<pre><code>[AllowAnonymous]
public ActionResult ExternalLoginCallbackRedirect(string returnUrl)
{
 return RedirectPermanent("/Account/ExternalLoginCallback");
}
</code></pre>

A template project has been posted on GitHub for reference: <a href="https://github.com/Pritchard/Test-AspNetGoogleOAuth2Authentication" rel="nofollow">https://github.com/Pritchard/Test-AspNetGoogleOAuth2Authentication</a>

blocks|key|160008|text|到目前为止给出的答案让我走上了一条非常黑暗的道路，我希望我没有走过这条路……解决方案很简单，请确保以下3个条件匹配：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|160009|1)在谷歌宣誓凭证(https://console.developers.google.com/)中：|offset|length|160010|160011|重定向URIS具有https://localhost:44300/Account/ExternalLoginCallback+(将您的端口固定到您正在使用的任何端口)|unordered-list-item|160012|160013|2)在AccountController中|style|CODE|160014|[HttpPost]
[ValidateAntiForgeryToken]
public+ActionResult+ExternalLogin(string+provider,+string+returnUrl)
{
++++return+new+ChallengeResult(provider,+
++++++++Url.Action("ExternalLoginCallback",+"Account",+
++++++++new+{+ReturnUrl+=+returnUrl+}));
}|code-block|syntax|javascript|160015|请注意，操作是"ExternalLoginCallback“|160016|3)在App_Start\Startup.Auth.cs中|160017|app.UseGoogleAuthentication(new+GoogleOAuth2AuthenticationOptions()
{
++++ClientId+=+"yourclientid.apps.googleusercontent.com",
++++ClientSecret+=+"yoursecret",
++++Provider+=+new+GoogleOAuth2AuthenticationProvider(),
++++CallbackPath+=+new+PathString("/Account/ExternalLoginCallback")
});|160018|请注意，CallbackPath的PathString与其他2个相同|160019|最后，如果仍然无法获取，请在应用程序Web.config中将身份验证模式设置为无|160020|<authentication+mode="None"+/>|160021|以获取有关该问题的更多详细信息。|160022|entityMap|0|LINK|mutability|MUTABLE|url|https://console.developers.google.com/|1|https://localhost:44300/Account/ExternalLoginCallback^0|0|A|12|0|0|0|9|1H|1|0|0|3|H|0|0|0|3|P|0|0|4|C|H|A|0|I|A|0|0|0^^$0|@$1|2|3|4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1I|8|@]|9|@$D|1J|E|1K|1|1L]]|A|$]]|$1|F|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|1N|8|@]|9|@$D|1O|E|1P|1|1Q]]|A|$]]|$1|J|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1S|8|@$D|1T|E|1U|M|N]]|9|@]|A|$]]|$1|O|3|P|5|Q|7|1V|8|@]|9|@]|A|$R|S]]|$1|T|3|U|5|6|7|1W|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1X|8|@$D|1Y|E|1Z|M|N]]|9|@]|A|$]]|$1|X|3|Y|5|Q|7|20|8|@]|9|@]|A|$R|S]]|$1|Z|3|10|5|6|7|21|8|@$D|22|E|23|M|N]|$D|24|E|25|M|N]]|9|@]|A|$]]|$1|11|3|12|5|6|7|26|8|@$D|27|E|28|M|N]]|9|@]|A|$]]|$1|13|3|14|5|Q|7|29|8|@]|9|@]|A|$R|S]]|$1|15|3|16|5|6|7|2A|8|@]|9|@]|A|$]]|$1|17|3|-4|5|6|7|2B|8|@]|9|@]|A|$]]]|18|$19|$5|1A|1B|1C|A|$1D|1E]]|1F|$5|1A|1B|1C|A|$1D|1G]]]]

The answers given so far led me down a really dark path that I wish I had not traveled... the solution is simple make sure that the following 3 things match:

1) In the Google OATH Credentials (<a href="https://console.developers.google.com/" rel="nofollow">https://console.developers.google.com/</a>):

<ul>
<li>REDIRECT URIS has <a href="https://localhost:44300/Account/ExternalLoginCallback" rel="nofollow">https://localhost:44300/Account/ExternalLoginCallback</a>
 (Fix your port to whatever you're using)</li>
</ul>

2) In your <code>AccountController</code>:

<pre><code>[HttpPost]
[ValidateAntiForgeryToken]
public ActionResult ExternalLogin(string provider, string returnUrl)
{
 return new ChallengeResult(provider, 
 Url.Action("ExternalLoginCallback", "Account", 
 new { ReturnUrl = returnUrl }));
}
</code></pre>

Notice the Action is "ExternalLoginCallback"

3) In your <code>App_Start\Startup.Auth.cs</code>

<pre><code>app.UseGoogleAuthentication(new GoogleOAuth2AuthenticationOptions()
{
 ClientId = "yourclientid.apps.googleusercontent.com",
 ClientSecret = "yoursecret",
 Provider = new GoogleOAuth2AuthenticationProvider(),
 CallbackPath = new PathString("/Account/ExternalLoginCallback")
});
</code></pre>

Notice the <code>CallbackPath</code> again has the same <code>PathString</code> as the other 2

Finally, if you're still not getting it, set your authentication mode to None in your app <code>Web.config</code>

<pre><code>&lt;authentication mode="None" /&gt;
</code></pre>

to get some more details about the issue.

blocks|key|163673|text|不需要在UseGoogleAuthentication中指定CallbackPath：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|163674|CallbackPath+=+new+PathString("/Account/ExternalLoginCallback")|code-block|syntax|javascript|163675|只需保留授权重定向URIs的谷歌设置为：|163676|163677|+http(s)://yoururl:orPort/signin-google|blockquote|BOLD|163678|163679|163680|Owin在内部处理signin-google并重定向到ChallengeResult类的代码中提到的redirectUri。即Account/ExternalLoginCallback。|163681|entityMap^0|4|N|U|C|0|0|9|4|0|0|Q|D|0|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|12|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|16|8|@]|D|@]|E|$]]|$1|N|3|O|5|P|7|17|8|@$9|18|A|19|B|Q]]|D|@]|E|$]]|$1|R|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|1C|8|@]|D|@]|E|$]]|$1|V|3|-4|5|6|7|1D|8|@]|D|@]|E|$]]]|W|$]]

There is no need to specify <code>CallbackPath</code> in <code>UseGoogleAuthentication</code>: 

<pre><code>CallbackPath = new PathString("/Account/ExternalLoginCallback")
</code></pre>

Just keep the Google setting for Authorized redirect <code>URIs</code> as:

<blockquote>
 http(s)://yoururl:orPort/signin-google
</blockquote>

Owin handles signin-google internally and redirects to the redirectUri as mentioned in your code for ChallengeResult class. Which is Account/ExternalLoginCallback.

blocks|key|161066|text|从教程中得到了它的工作香草，只需一个简单的更改-只需将其发布到此方法的任何块。我认为在这种情况下与oauth2相关的问题在最新的模板/apis中得到了很大程度的充实-我的意思是，如果你是从头开始的，你可能会走运-继续阅读：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|161067|我刚刚完成了这个教程https://azure.microsoft.com/en-us/documentation/articles/web-sites-dotnet-deploy-aspnet-mvc-app-membership-oauth-sql-database/|offset|length|161068|并且还引用了http://blogs.msdn.com/b/webdev/archive/2014/07/02/changes-to-google-oauth-2-0-and-updates-in-google-middleware-for-3-0-0-rc-release.aspx|161069|只有一个变化：它起作用了，但只有在最新版本的google%2B开发者站点中启用了google+apis之后才能工作。|style|BOLD|161070|(只需转到google+api库管理器，登录并在api目录中搜索google%2B+api)。|161071|注意:对于我来说，默认情况下Google%2B接口是禁用的。|161072|我没有做任何其他独特的事情。|161073|干杯|161074|entityMap|0|LINK|mutability|MUTABLE|url|https://azure.microsoft.com/en-us/documentation/articles/web-sites-dotnet-deploy-aspnet-mvc-app-membership-oauth-sql-database/|1|http://blogs.msdn.com/b/webdev/archive/2014/07/02/changes-to-google-oauth-2-0-and-updates-in-google-middleware-for-3-0-0-rc-release.aspx^0|0|A|3I|0|0|6|3S|1|0|0|7|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@$D|15|E|16|1|17]]|A|$]]|$1|F|3|G|5|6|7|18|8|@]|9|@$D|19|E|1A|1|1B]]|A|$]]|$1|H|3|I|5|6|7|1C|8|@$D|1D|E|1E|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1F|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1G|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1H|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1I|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10]]|11|$5|W|X|Y|A|$Z|12]]]]

Got it working vanilla from the tutorial with ONE simple change - just posting this for any nubes to this approach. I think the problems related to oauth2 in this instance are largely fleshed out in the latest templates/apis - what I mean is, if you are starting from scratch, you may be in luck - read on:

I JUST did this tutorial 
<a href="https://azure.microsoft.com/en-us/documentation/articles/web-sites-dotnet-deploy-aspnet-mvc-app-membership-oauth-sql-database/" rel="nofollow">https://azure.microsoft.com/en-us/documentation/articles/web-sites-dotnet-deploy-aspnet-mvc-app-membership-oauth-sql-database/</a>

and referenced this also
<a href="http://blogs.msdn.com/b/webdev/archive/2014/07/02/changes-to-google-oauth-2-0-and-updates-in-google-middleware-for-3-0-0-rc-release.aspx" rel="nofollow">http://blogs.msdn.com/b/webdev/archive/2014/07/02/changes-to-google-oauth-2-0-and-updates-in-google-middleware-for-3-0-0-rc-release.aspx</a>

The one change:
it worked but ONLY after enabling google+ apis in the newest version of the google developer site. 

(Just go to google api lib manager, sign in and search the apis directory for the google+ api). 
Note: for me the Google+ api was disabled by default. 

I did nothing else unique.

Cheers

I decided to give the new Google Oauth2 middleware a try and it has pretty much broken everything. Here is my provider config from startup.auth.cs.. When turned on, all of the providers including the google provider get a 500 internal server on Challenge. However the details of the internal server error are not available and I cant figure out how to turn on any debugging or tracing for the Katana middleware. Seems to me like they were in a rush to get the google Oauth middleware out the door.

<pre><code> //// GOOGLE
 var googleOptions = new GoogleOAuth2AuthenticationOptions
 {
 ClientId = "228",
 ClientSecret = "k",
 CallbackPath = new PathString("/users/epsignin")
 SignInAsAuthenticationType = DefaultAuthenticationTypes.ExternalCookie,
 Provider = new GoogleOAuth2AuthenticationProvider
 {
 OnAuthenticated = context =&gt;
 {
 foreach (var x in context.User)
 {
 string claimType = string.Format("urn:google:{0}", x.Key);
 string claimValue = x.Value.ToString();
 if (!context.Identity.HasClaim(claimType, claimValue))
 context.Identity.AddClaim(new Claim(claimType, claimValue, XmlSchemaString, "Google"));
 }
 return Task.FromResult(0);
 }
 }
 };

 app.UseGoogleAuthentication(googleOptions);
</code></pre>

ActionMethod Code:

<pre><code> [AllowAnonymous]
 public ActionResult ExternalProviderSignIn(string provider, string returnUrl)
 {
 var ctx = Request.GetOwinContext();
 ctx.Authentication.Challenge(
 new AuthenticationProperties
 {
 RedirectUri = Url.Action("EPSignIn", new { provider })
 },
 provider);
 return new HttpUnauthorizedResult();
 }
</code></pre>

GoogleOauth2 Issue Getting Internal Server 500 error

身份验证

中间件

服务器

调试器

路由

GitHub

我决定试一试新的谷歌Oauth2中间件，它几乎打破了一切。这是我从startup.auth.cs获得的提供程序配置。打开后，包括google提供商在内的所有提供商都会在Challenge上获得一个500内部服务器。但是，内部服务器错误的详细信息不可用，我也不知道如何打开Katana中间件的调试或跟踪。在我看来，他们似乎...

问获取内部服务器500错误时出现GoogleOauth2问题
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问获取内部服务器500错误时出现GoogleOauth2问题EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问获取内部服务器500错误时出现GoogleOauth2问题
EN