Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support ASP.NET Core 2.0 (Auth 2.0)

See original GitHub issue

It looks like instead of registering auth middleware per scheme, there’s just one auth middleware and different auth schemes are added by calling services.AddScheme<TOptions, THandler>.

See: https://github.com/aspnet/Announcements/issues/232

Issue Analytics

State:
Created 6 years ago
Comments:12 (8 by maintainers)

Top GitHub Comments

5reactions

kevinchaletcommented, May 14, 2017

Correct me if I’m wrong (and I don’t doubt that I am), but isn’t the majority of the change just moving where you provide your AuthHandler to DI (AddScheme) rather than having a middleware do it?

Well, it’s indeed the most visible change, but it’s not the only one: there’s a bunch of API signatures changes and things that are not possible at all in the new world for which we’ll have to find different approaches (e.g authentication middleware selection via pipeline branching: https://github.com/openiddict/openiddict-samples/blob/master/samples/CodeFlow/AuthorizationServer/Startup.cs#L103-L158).

There’s nothing complicated, just time that must be spent to port the validation/introspection middleware, ASOS and OpenIddict 😄

4reactions

kevinchaletcommented, May 11, 2017

The new authentication stack - that I helped design - is so different than the previous one that it will require massive changes in both ASOS and OpenIddict. I’ll probably have something ready for 2.0-preview2.

https://github.com/OrchardCMS/Orchard2/issues/730#issuecomment-298250282