API key authentication implementation #17800
Draft
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.
See GH-17563
Adds API key authentication support. Key components include the following:
ApiKeiis a data model consisting of ID and secret parts.ApiKeyprovides method for generating new instance randomly;ApiKeyDigesthandles hashing API key secret part and comparing secret with existing hash. This component closely resemblesPasswordEncoderfunctionality;ApiKeySearchServiceallows framework user to hook into the API key authentication lifecycle. This component closely resemblesUserDetailsServicefunctionality;ApiKeyAuthenticationProviderhandles API key authentication aspects;ApiKeyAuthenticationFilterintercepts incoming requests and hands control over toAuthenticationManagerthe same way other similar filters do (e.g.,BasicAuthenticationFilter).This is a work-in-progress, it's far from finish (no reactive stack support, no tests, etc.), but it catches the way it should work from my perspective.