Question

I have two controllers;

• AccountController : Controller //For accounts <-- MVC
• ItemController : ApiController //For Items <-- WEB API

The accounts controller is for all intents and purposes a pretty standard implementation of the Accounts code, the only major difference is that it’s using a Custom MembershipProvider. On the accounts controller I also have one other Action:

[Authorize]
public ActionResult Bleh(){ return View(); }

Which if I attempt to get to:

http://localhost/Account/Bleh

Redirects me (as expected) to the Login page, which after logging in, returns me back to the Bleh page. All good. The problem is on the ItemController, I have an Action which too has an Authorize attribute on it:

[Authorize]
public HttpResponseMessage PostItem(Item item) { /**/ }

Going to this before logging in returns a 401 – Unauthorized – which again is as expected, but after logging in, it still returns a 401. I can’t see why this is the case.

Am I missing any configuration elements? Routing? N.E. Other?

I was under the impression that Web Api would pick up the Forms Authentication in the same way as MVC, and I know the authentication is working as the MVC one is working.

Answer 1

I have rebuilt the application from scratch, and the forms code is working as expected now. I cannot for the life of me see any difference between my original code and the new code. I suspect maybe something in a config file somewhere, but after a pretty substantial amount of time it eludes me.