feat(api): enable authentication for control-api #4197
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.
What this PR changes/adds
Permit control-api authentication via extensions.
Server side:
ApiAuthenticationRegistry
service has been introduced that can be used both formanagement-api
andcontrol-api
, it is used to register anAuthenticationService
for the specified context.Client side:
ControlClientAuthenticationProvider
can be registered to provide the authentication headers. It has already been injected on all the "control-api client" services to decorate the request with the headers (by default it returns an empty map)Why it does that
authentication
Further notes
control-api
,management-api
, ... as done for the transformers, but, the context alias as it is handled by the configuration is in the form ofcontrol
,management
. It would be better to uniform to a single convention, and the latter would be preferred. Subsequent PR will comeLinked Issue(s)
Closes #839
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.