<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Aspnetcore on Matt Thornton</title>
    <link>http://localhost:1313/tags/aspnetcore/</link>
    <description>Recent content in Aspnetcore on Matt Thornton</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Wed, 04 Mar 2020 15:16:49 +0000</lastBuildDate><atom:link href="http://localhost:1313/tags/aspnetcore/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>ASP.NET Core OAuth Facebook cancel causes 500 fix</title>
      <link>http://localhost:1313/tech/asp-net-core-oauth-facebook-cancel-causes-500-fix/</link>
      <pubDate>Wed, 04 Mar 2020 15:16:49 +0000</pubDate>
      
      <guid>http://localhost:1313/tech/asp-net-core-oauth-facebook-cancel-causes-500-fix/</guid>
      
        <description>&lt;p&gt;If you&amp;rsquo;re using ASP.NET Core built-in authentication to allow your users to sign up / login to your web application using alternative providers, Microsoft provides various out of the box, such as Microsoft, Google, Twitter and Facebook.&lt;/p&gt;
&lt;p&gt;Chances are you have something like the following in your startup.cs&lt;/p&gt;
&lt;pre class=&#34;wp-block-code&#34;&gt;&lt;code&gt;services.AddFacebook(options=&gt; ...)&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This works pretty nicely. All you need are you keys and secrets (hello Urban Cookie Collective) and all should rock.&lt;/p&gt;
&lt;p&gt;However, an issue arises if your user clicks ‘Sign in with &lt;x&gt;&amp;rsquo;, which (if they are not already signed-in) takes them to that app to sign in, but if they then cancel that (e.g., clicking the ‘Not Now&amp;rsquo; link on the Facebook screen) can result in a ghastly 500 error.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>