Remove Spring Security class dependency on ProblemAutoConfiguration #513
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.
Description
0.26.0 changed the way how the default
ExceptionHandling
implementation is instantiated. As we have projects, which switched to Fabric Gateway for authentication and in consequence removed Spring Security dependencies, the latest version of the library does not work as in this case the classWebSecurityConfigurer
is not available on the classpath.Motivation and Context
Fixes dependent projects not using Spring Security due to changes introduced in #413.
Types of changes
Checklist: