Skip to main content

How to authenticate a console app to an ASP.NET MVC 4 web site

In this post I will show you how to authenticate an application to an ASP.NET MVC web site that uses forms authentication. This sounds a bit weird, but as I found out on the web, this is a fairly common thing to do these days.

The most common scenario where people want to do this is, is when they want to consume an ASP.NET MVC web site as if it was a Web API, to get resources that are already in place and are accessible thru controller’s actions.

There is couple of ways of doing this, and it is pretty easy until you need to authenticate the request in order to get those resources. 

The web site we are working on uses Forms Authentication, this means that when a request arrives, the ASP.NET infrastructure is going to see if this request is authenticated or not, if is not, it will redirect the request to the login page. While this works fine for web pages, is not so good for APIs. Down below I’ll show how to authenticate a client to a login page using the HttpClient class. 

* note: I'm assuming that you 're familiar with the with the "internet app templete" that comes with mvc 4.0, If not, grab the sample project from this post and take a look at the AccountController class.

This is how you can authenticate a request that otherwise it would be redirected to a login page. 

Once you have done that, you have client that can issue authenticated requests to your website. 

* note that I’m using the same HttpClient instance that executed the login request. If you don’t do it this way, it won’t work at all.

You can get the sample app from github

The repository contains a solution with two projects, an ASP.NET MCV 4 web site and a console app that consume the web site as if it was an API.

The web site it's also published on Windows Azure, so you can test the code in an environment other than localhost. Just change this line in the console app config.


  1. Working for Unit test too? the unit test (MSTest) consume the web site as if it was an API?

    1. Hmm, I'm clueless on this one; and to be honest, I never have used MSTest. Most .NET testing frameworks suck big time when it comes to async stuff, so I'll guess, no; but I'll go to give it a try and let you know if it works out.

      PS: While I do most of my work using TDD, In general I tend to focus on domain logic rather than HTTP calls, so keep in mind I'm not an expert on that subject.


Post a Comment

Popular posts from this blog

Moving to Medium

It's been a long time since I want to give medium a try, and finally, I made some time to do it. To get started on the new platform, I'll be doing series on "Getting programming concepts, languages and tools". If it sounds interesting to you, please take a look at the first post  Getting AWK  and spread the word if you like it. I'm not going to migrate old entries to the new web site. They will remain here safe and sound! As usual, thanks for reading!

Working with unattended reports

In this post I‘ll show you how to create reports that NRapid will execute into an unattended mode. I strongly recommend using this kind of reports in automation scenarios only , and let the user see the print preview dialog in the rest of cases. The only difference between this reports and the standard ones, is that you will cannot make use of dialogs, the runtime will always pass in empty views to the ConfigureReport method. The ConfigureReport method will be executed, but you will have to grab the arguments from somewhere else. The execution pipeline is the same that NRapid uses for standard reports. This is the code to print out the whole list of categories in a dialogless mode. Notice that this report inherits from UnattendedReport class, this class tells to NRapid “run the report unattended”. Also notice that this class comes with a convenience method to configure the report with no arguments. You still can override the one that gets the view data but you will always

How to create MS Word documents from Office templates using C#

The OpenXML SDK allows you to do pretty much anything you want with office files such as Excel, Word, etc… While many people like this library, I found it complex, unintuitive and poorly documented, not to mention the awful xml format that uses under the hood to represent the documents, styles, etc. So I decided not to use it and build my own solution. If you, like me, don’t like that library, you will find in this post an alternative approach to build word documents from templates using c#. A neat trick to work with Office is to use the macro recorder to understand how things work. The macro recorder allows you to start a macro, do something by hand, stop it, and then take a look at the generated VBA code. Once you do this, you are pretty much set. This is how it looks the template I’am going to use. Note: save the file as a Word template (.dotx) This is the code to create Word documents from C#: By running the code, you should get a document that looks