Almost 2 years ago I wrote a blog post about using the generic OAuth provider in ASP.NET Core. A lot has changed since then, so I thought it might be a good time to revisit this. For this blog post, we will create a simple website which allows users to sign in with their GitHub credentials. I will also demonstrate how we can store the access token received from GitHub to make GitHub API calls using Octokit.
When developing a Webhook for a GitHub application, you may want to make calls to the GitHub API. In order to do this you will need to have a Bearer token to authorize the calls. In a typical scenario, you would obtain a token as part of the user authorization flow, but when developing a webhook for a GitHub application things work a bit differently as there is no interactive user involved.
Update: 19 May 2015 - You can view an updated video version of this on my AspnetCasts YouTube channel. The updated version is targeted for use with ASP.NET MVC 5 and ASP.NET Identity. Update: 1 April 2015 - The latest and most up to date version of this guide is available on the OAuth for ASP.NET website Turns out I had some extra time on my hands - or maybe I am just procrastinating.
Microsoft recently made Git source control available as an alternative source control provider on Team Foundation Service. I decided to move my existing private repositories from Github to TFS. This video describes the process.