<EDIT> A few days ago they changed it again….
Instead of .AddCookieAuthentication(….
It’s now just .AddCookie();
Or rather Aspnetcore 2.0.0-preview2-006497 since they changed it again….
First, download the latest bits from .NET Core 2.0 and install it.
Open a developer command prompt and check version with
It should say 2.0.0-preview2-006497 for you to be sure that my instructions will work 🙂
Create a new folder for your project and create a new mvc project with
dotnet new mvc
After it is done we will add the dependencies for authentication
dotnet add package Microsoft.AspNetCore.Authentication -v “2.0.0-preview2-final”
dotnet add package Microsoft.AspNetCore.Http -v “2.0.0-preview2-final”
Now we add, one by one the authentication providers we want. In Startup.cs in ConfigureServices:
The biggest change in this version is perhaps that you only add
To the pipeline in the Configure method.
So. Done with that part. Oh, forgot the usings. Add these to the top
A few more than necessary but I will get to them. Now the project should start with
But it still allows for anonymous access.
Add the attribute [Authorize] to your HomeController together with a matching using like so:
So. Again start the project and browse to http://localhost:5000/. You will be redirected to /home/login and get an error since that page does not exist (yet).
In the HomeController.cs add this code
This is used when you manage all the users and passwords yourself (please don’t).
But seriously, sometimes you have an old back-end system that you are building a new front-web for and it has all the user info.
I created a super simplistic view for this action. Create a new file in the folder Views/Home called Login.cshtml with this content
Told you. Simplistic. Make sure these “usings” are in place in your HomeController.cs
Now, go back up to the project root folder and run the application again. This time the login page is displayed. If you try to login with your hard coded username and password you will be logged in and redirected to /. If you inspect the ClaimsPrincipal when debugging you will see that your claims are visible under the Identity-property.
Great. Let the user logout as well.
Add a link somewhere that redirects the user to /home/logout. Done.
So. How about Twitter?
First, add a new app at apps.twitter.com . Click “Create new app” and fill out the form. You can set callback url to localhost:5000. Go to the Keys and Access Tokens-tab and copy them to your appSettings.json file
Please note that if you intend to publish the code somewhere, don’t store these credentials here. Use secrets instead.
Remember the fancy looking login page? The Twitter-link was /login-twitter. Just because it is fun I will hard-wire this url into the processing pipeline.
So. Head over to Startup.cs and paste this code into the Configure-method.
Now you redirected to a Twitter page and depending if you are already logged into Twitter or not the page either asks you to logon or only to authorize your new app to connect to Twitter.
Tip: If you want to dress the current user with more claims than Twitter sent, you can always add them. Like your internal user id of that Twitter-identified user.