Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a WIP!
The goal is for a worker component to be able to attest to a remote entity (API, STS) that it is part of the golem environment. The remote entity can make their decisions based on the attested claims to e.g. allow API calls or in case of a secrets vault unlock the secret just for a specific component in a specific account.
It adds a API for components to retrieve a signed JWT with claims about the workers account, component id, worker name.
golem:api/identity.{get-token}
Both must share the configuration with the keys. The worker service just needs to get the public information to display it on the endpoints while the worker executor actually needs the private parts to sign the JWT.
There is a lot to be done and cleaned up. I wanted to make it public for awareness and to see if this is of interest to the project.