ThreadLocal based Inspektr PrincipalResolver #1957
Merged
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.
This PR introduces a ThreadLocal based storage for current Authentication object as well as Inspektr PrincipalResolver based on that state. This is in response to already complex and brittle current Joinpoint-based PrincipalResolver that does complex Joinpoint parsing and is very tightly coupled to CAS API which in the latest iterations has changed significantly and therefore this resolver is not able to resolve proper principal at all the configured audit points.
This PR also has the side effect that this ThreadLocal holder for current authentication could be used by other interested downstream components without tight coupling to all the internal CAS components just to get a currently in-progress authentication/principal, should they need it.