owin

My application uses self-hosting feature of ASP.NET Web API . NuGet package name I use is Microsoft.AspNet.WebApi.SelfHost. I used following example as a base. Following code works for me to launch host on ipv4 localhost endpoint: WebApp.Start<Startup>("http://127.0.0.1:43666"); What do I enter if I want to specify ipv6 address? "http://[::1]:43666" does not work. Exception thrown is [reformatted]: System.Net.HttpListenerException: The network location cannot be reached. For information ..about network troubleshooting, see Windows Help at System.Net.HttpListener.AddAllPrefixes() at System.Net

There are multiple question I have around self-hosting Self Hosting Nuget There are 2 nuget which provide self hosting : Microsoft.AspNet.WebApi.OwinSelfHost and Microsoft.AspNet.WebApi.SelfHost , so does microsoft have 2 implementation of self hosting?? or they are same?? Owin or Kitana the name of nuget is Microsoft.AspNet.WebApi.OwinSelfHost has OWIN, but as far as I read Owin is an interface and Kitana an implementation, what is the name of the nuget for implementation?? Hosting in Production I have managed to run the example by creating a console. But when deploying to prod, how to deploy

I noticed yesterday that my Facebook login for my website has stopped working. This has been working great for the last 2 months, as far as I am aware I have not changed anything. I have tried everything I can on links such as: - as well as many more... ASP.NET MVC5 OWIN Facebook authentication suddenly not working I have noticed that the Stack Overflow Facebook auth has also stopped working. Has anyone else noticed this and found any solution? It's worth noting I am using azure app services to host. But this issue is also found when I am using localhost. My current setup looks like this... in

In my WebAPI project I'm using Owin.Security.OAuth to add JWT authentication. Inside GrantResourceOwnerCredentials of my OAuthProvider I'm setting errors using below line: context.SetError("invalid_grant", "Account locked."); this is returned to client as: { "error": "invalid_grant", "error_description": "Account locked." } after user gets authenticated and he tries to do "normal" request to one of my controllers he gets below response when model is invalid (using FluentValidation): { "message": "The request is invalid.", "modelState": { "client.Email": [ "Email is not valid." ], "client

I have questions upon using the new ASP.Net OpenID Connect framework while adding new Claims during the authentication pipeline as shown in the code below. I'm not sure just how much 'magic' is happening behind the scenes. I think most of my questions center around not knowing much about OWIN authentication middleware as opposed to OpenID Connect. Q1. Should I be manually setting HttpContext.Current.User and Thread.CurrentPrincipal from OwinContext.Authentication.User ? Q2. I want the ability to add object types to claims like I used to with System.IdentityModel.Claims.Claim . The new System

I'm using the owin TestServer class to unit test my web api. It's working great except that I'm unsure how to authenticate requests, so I can't really test endpoints that require authentication, other than to make sure that unauthenticated requests are unauthorized. I am configuring WebApi to use only bearer token authentication as indicated here: // Web API configuration and services // Configure Web API to use only bearer token authentication. config.SuppressDefaultHostAuthentication(); config.Filters.Add(new HostAuthenticationFilter(OAuthDefaults.AuthenticationType)); Any ideas how I could