feat: allow to perform attestations with user token #1883
Merged
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 PR adds support to perform attestations with an user token, the change basically includes two things
1 - Chain a user-token authenticator to the JWTMulti cascade-based middleware we use during attestations
2 - Add an additional middleware to set the required user and org context required in the service layer.
About 2: I managed to implement it basically reusing the existing middlewares just doing wrap calling, additionally we do an authorization check to make sure read only users can not attest in the org.
Demo
I have three orgs with organization-2 set as default client-side
if I perform an attestation,
organization-2
will be pickedwhich can be overridden either manually with the
--org
flagcloses #1003