You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.
Currently, we have the default forwarder server key baked into the funcx-endpoint. However, this creates a couple of issues:
Cycling keys means you have to roll out a new funcx-endpoint release with the updated key.
If the user has to connect to a private/dev funcx deployments, they have to manually copy server keys to the certificates dir.
Alternatively, we could have the web-service return the forwarder-service key upon endpoint registration. This would allow each individual forwarder to have its own local server key generated at the service start and passed back to the endpoint.
The text was updated successfully, but these errors were encountered:
Currently, we have the default forwarder server key baked into the
funcx-endpoint
. However, this creates a couple of issues:funcx-endpoint
release with the updated key.Alternatively, we could have the web-service return the forwarder-service key upon endpoint registration. This would allow each individual forwarder to have its own local server key generated at the service start and passed back to the endpoint.
The text was updated successfully, but these errors were encountered: