Allow to provide SecurityContextRepository and SecurityContextHolderStrategy to be used #230
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.
In this PR I added fields for a
SecurityContextRepository
and aSecurityContextHolderStrategy
und use them similar to AbstractAuthenticationProcessingFilter#successfulAuthentication to store theSecurityContext
in theSecurityContextRepository
. By default it usesRequestAttributeSecurityContextRepository
wich is the same as in theAbstractAuthenticationProcessingFilter
.To finally achieve the expected result for #185 we have to configure the
SpnegoAuthenticationProcessingFilter
with at least aHttpSessionSecurityContextRepository
or better (as far as I can tell from checking what spring-security is doing) withnew DelegatingSecurityContextRepository(new RequestAttributeSecurityContextRepository(), new HttpSessionSecurityContextRepository())
. Usinghttp.getConfigurer(SecurityContextConfigurer.class);
should also work if thehttp
object is available when creating the SPNEGO Filter.Fixes #185