You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 13, 2018. It is now read-only.
Why does AuthenticationMiddleware take it's dependencies on the constructor and not on Invoke? Very hard to build handler with dependencies. Why would TearDownAsync be internal!?!? This prevents me from writing my own AuthentionMiddleware and using proper DI pattern for Middleware.
The text was updated successfully, but these errors were encountered:
Yeah we are aware of the issues with the current design, we working on addressing these in the next version, you should be able implement a handler with normal dependencies on the new stack, see #1113
Is there a way to inject IOptions that is parsing the application settings into an AuthenticationHandler (instanciated by an AuthenticationMiddleware) in asp.net core 1.x? Or at least a workaround?
Why does AuthenticationMiddleware take it's dependencies on the constructor and not on Invoke? Very hard to build handler with dependencies. Why would TearDownAsync be internal!?!? This prevents me from writing my own AuthentionMiddleware and using proper DI pattern for Middleware.
The text was updated successfully, but these errors were encountered: