Error when trying to use JWT for ASP NET Owin Authentication?
I had the following configuration:
owin
SignalR Hub-2-Hub Communication with SQL Backplane in ASP.NET Owin
I have an ASP.NET Owin Web Api which is load balanced, which means there are multiple instances of it which don´t know each other. The web api hosts a SignalR hub with an SQL Server Backplane (for synchronising between instances), so clients can exchange messages regardless of which instance of the web api they are connected to. Everything working so far.
OWin Appbuilder rebuilding the app 70 -125 times per event
I’ve been following several tutorial on integrating the OWin identity in my ASP.net app, for instance this one
What mechanism does OWIN use to determine that a user is authenticated before reading their claims?
I’ve launched the sample project for ASP.Net MVC that provides single sign-on against Active Directory, and am using this Microsoft tutorial for reference.
ASP.NET_SessionId + OWIN Cookies do not send to browser
I have a strange problem with using Owin cookie authentication.
Do I need a Global.asax.cs file at all if I’m using an OWIN Startup.cs class and move all configuration there?
Let’s say for example in a brand new ASP.NET MVC 5 application made from the MVC with Individual Accounts template, if I delete the Global.asax.cs class and move it’s configuration code to Startup.cs Configuration() method as follow, what are the downsides?
Can OWIN middleware use the http session?
I had a little bit of code that I was duplicating for ASP.NET and SignalR and I decided to rewrite it as OWIN middleware to remove this duplication.
Disable *all* exception handling in ASP.NET Web API 2 (to make room for my own)?
I want to wire up exception handling in a middleware component, something like this:
Too many cookies OpenIdConnect.nonce cause error page “Bad Request – Request Too Long”
I’m using OWIN / OAuth with OpenId Connect authentication (Microsoft.Owin.Security.OpenIdConnect) in a C# ASP MVC web app. The SSO login with Microsoft account basically works, but from time to time I’m getting an error page on the browser that says Bad Request - Request Too Long.
Login page on different domain
I am completely new to OWIN authentication, and I must be misunderstanding how everything works, but I can’t find this mentioned anywhere.