Description

We have the Set Security User Processor, that is able to add information about the authenticated user that performs the request.

We could do something similar when an API key is used to authenticate instead of a regular user.

Proposal

We can create a new processor (or extend the Set Security User Processor) to make API key information available to the ingest pipeline.

We should expose the name field. We can also expose other fields if they could be relevant.