Consider resolving IAuthenticationSchemeProvider from DI in Invoke in AuthenticationMiddleware

[brockallen]

In short, accepting the IAuthenticationSchemeProvider as a ctor to the AuthenticationMiddleware forces it to be a singleton. I know the default is deigned that way and put in DI that way, but if someone wants to replace it (say with something that hits a DB) then it's difficult.

[Tratcher]

Interesting. You wouldn't be able to use most of the AddFacebook/OIDC extensions with that pattern as they all rely on the singleton. It would be a pretty sharp one-or-the-other divergence.

You may be better off replacing the IAuthenticationService with something that doesn't use IAuthenticationSchemeProvider at all, and IAuthenticationService is already scoped.

[brockallen]

I think whatever larger multi-tenant solution is finally presented (assuming it's eventually done as what Damian said here: aspnet/Security#1718), that would prolly address my issue and provide me a workaround.

In the short term, I'll see if hooking in at the authN service gets me what I need.

[Eilon]

Parking in backlog. We will look into this again when we eventually embark on proper multi-tenant support.

[dasiths]

I gave an example about how this could be useful in #4126.

[dasiths]

@Eilon any updates on this?