Instead of hardcoding the JWT secrets in each of the clients, we could make the dappmanager responsible for their generation and distribution. The process is defined below:
On start, dappmanager generates a random JWT per network and stores them
There must be an allow list that defines which services have access to each secret. This could be inferred from the list of clients to be shown in the stakers
3A. The Dappmanager will expose an API endpoint that will return the secret in case that the request source is one of the allowed ones
3B. The Dappmanager will inject the value of that secret into the compose file of any client included in the allow list at installation time
Instead of hardcoding the JWT secrets in each of the clients, we could make the dappmanager responsible for their generation and distribution. The process is defined below:
On start, dappmanager generates a random JWT per network and stores them
There must be an allow list that defines which services have access to each secret. This could be inferred from the list of clients to be shown in the stakers
3A. The Dappmanager will expose an API endpoint that will return the secret in case that the request source is one of the allowed ones
3B. The Dappmanager will inject the value of that secret into the compose file of any client included in the allow list at installation time