Hi,
I agree, we need a solution for that.
Both of your approaches are feasible.
I was thinking about an option c) which is similar to a).
So the idea is to provide the API key via the docker-compose file, but without
generating it in the UI first.
Therefore, we would need a way in the backend
Hi,
good points and a relevant topic.
Do you still consider having an unauthenticated way in case getting these API
keys
would end up involving several additional steps to the installation process?
I see both options as feasible - either create/manage keys via the UI or have a
mechanism
Hi all,
I have a question concerning the authentication of some of our services
(pipeline element containers and adapter containers) that make use of features
from the backend/core via REST interfaces.
For instance, the DashboardSink uses an API endpoint from the core to create a
new
