Capturing login event so I can cache other user information
I’ve built a web application. When I built it I ticked ‘Organizational Accounts’
owin
How to plug my Autofac container into ASP. NET Identity 2.1
I have been looking into the new features of the new version of ASP.NET Identity 2.1 and one of its enhancements is the new IoC features integrated into the OWIN Middleware.
One of the sentences that I looked in the examples is this one:
How do I ignore the Identity Framework magic and just use the OWIN auth middleware to get the claims I seek?
The OWIN middleware stuff to integrate third-party logins to your ASP.NET app is very cool, but I can’t seem to figure out how to tear it out from the new ID framework that replaces the crappy Membership API. I’m not interested in persisting the resulting claims and user info in that EF-based data persistence, I just want the claims info so I can apply it to my own user accounts in existing projects. I don’t want to adopt the new ID framework just to take advantage of this stuff.
Data caching per request in Owin application
In traditional ASP.NET applications (that use System.Web), I’m able to cache data in
Alternative to use HttpContext in System.Web for Owin
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 get “Authorization has been denied for this request.” error message when using OWIN oAuth middleware (with separate Auth and Resource Server)
I am attempting to decouple my auth and resource server. I am following the example provided in this tutorial:
Require Authentication for all requests to an OWIN application
I am working with a self-hosted OWIN application and am trying to figure out how to require authentication/authorization for all requests (or arbitrary requests).
How to intercept 404 using Owin middleware
A few notes about my above test if anyone is intrested:
OWIN openid connect external login doesn’t execute specified callback url
I am using owin openid connect authentication where the authentication provider is hosted on a separate domain. The authentication process works nicely. I am able to view restricted pages upon successful login at the identity server.