katana

Startup.cs is a new way to initialize your app instead of Application_Start in Global.asax and it's fine. But is there a place to put my teardown logic, for example this: public class WebApiApplication : System.Web.HttpApplication { protected void Application_End() { // Release you ServiceBroker listener SqlDependency.Stop(connString); } } Looked in Microsoft.Owin namespace but it only seems to have OwinStartupAttribute . Does this mean that application lifecycle events are still processed by System.Web.HttpApplication instance and are not supported by OWIN specification? AppProperties , found

I am trying to understand the Asp.net Web Api Individual Accounts authentication and authorization. I have see several tutorials on the web including this one . In short, when a user agent provides username and password the API issues a token that the client will use in subsequent calls to the API for to identify itself. The user agent receives the token by making a request, typically to: http://example.com/Token . The path appears to be set in the Startup class like so: TokenEndpointPath = new PathString("/Token") My problem is, I can't find any controller methods that match that path. How

I've recently started looking at the new ASP.Net Identity framework and the Katana middleware, there's a surprising amount of code and documentation out there, but I'm seeing what appears to be a lot of conflicting information, which I guess is a result of the increasing frequency of code updates. I'm looking to use WsFederation Authentication against an internal ADFS 2 service, but the way the OWIN authentication pipeline works has me a little confused and I'm hoping someone can offer some definitive information. Specifically, I'm interested in the order in which middleware should be hooked

I am building self-hosted web server on this stack: OWIN Nancy Web Api 2 And I am using Microsoft.Owin.Security.Cookies from Katana for forms-like authentication. I got Set-Cookie header in response, but cookie don't being saved and not being included in next request. So what's the problem? What I am doing wrong? Owin startup: app.UseCookieAuthentication(new CookieAuthenticationOptions() { AuthenticationMode = AuthenticationMode.Active, AuthenticationType = "GM", CookieHttpOnly = true, CookieSecure = CookieSecureOption.SameAsRequest, CookiePath = "/", CookieName = CookieAuthenticationDefaults

ASP.NET authentication is now based on OWIN middleware that can be used on any OWIN-based host. ASP.NET Identity does not have any dependency on System.Web . I have an AuthorizeAttribute filter where I need to get the current user and add some properties to be retrieved later by action controllers. The problem is that I have to use the HttpContext wich belongs to System.Web. Is there any alternative of HttpContext for Owin? public class WebApiAuthorizeAttribute : AuthorizeAttribute { public override async Task OnAuthorizationAsync(HttpActionContext actionContext, CancellationToken