Description

To communicate via HTTP a Bearer token is needed which is generated at the startup and placed in validators-dir/api-token.txt. This HTTP communication is now required for some actions, e.g. after #3264, the only way now to update the fee recipient config is via Key Manager API.

The api-token.txt file is re-generated when restarting the service even if the file already exists in the expected location. This is problematic when automating the configuration of the system resulting in 403 HTTP responses due a change of the token.

This approach does not allow you to provision a specific token used by the different services that consume the validator and communicate via HTTP.

It would be better if we could provision the token as we already do with the JWT token needed for the EL communication.

Version

docker - v2.5.1-modern

Present Behaviour

The api-token.txt file is re-generated when restarting the service.

Expected Behaviour

Generate api-token.txt file only if is missing.