Update the OWIN client host to resolve the default cookie manager from the application builder when available #2328
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kevinchalet
force-pushed
the
cookie_manager
branch
from
eb7b24c to
26e8f44
Compare
…m the application builder when available
kevinchalet
force-pushed
the
cookie_manager
branch
from
26e8f44 to
90bba6c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It looks like Katana 4.2.3 is finally around the corner and will include aspnet/AspNetKatana#486.
This PR updates the OWIN client host to support resolving the default cookie manager from
IAppBuilderwhen the app builder is registered in the DI container (which is pretty much required when usingapp.UseMiddlewareFromContainer<T>()with any of the built-in Katana authentication middleware, as they all takeIAppBuilderas a constructor parameter).