zitadel/internal/api/grpc/resources/action/v3alpha
Stefan Benz 7caa43ab23
feat: action v2 signing (#8779)
# Which Problems Are Solved

The action v2 messages were didn't contain anything providing security
for the sent content.

# How the Problems Are Solved

Each Target now has a SigningKey, which can also be newly generated
through the API and returned at creation and through the Get-Endpoints.
There is now a HTTP header "Zitadel-Signature", which is generated with
the SigningKey and Payload, and also contains a timestamp to check with
a tolerance if the message took to long to sent.

# Additional Changes

The functionality to create and check the signature is provided in the
pkg/actions package, and can be reused in the SDK.

# Additional Context

Closes #7924

---------

Co-authored-by: Livio Spring <livio.a@gmail.com>
2024-11-28 10:06:52 +00:00
..
integration_test feat: action v2 signing (#8779) 2024-11-28 10:06:52 +00:00
execution.go fix(actions-v3): check feature flag on list methods (#8595) 2024-09-11 09:43:44 +00:00
query.go feat: action v2 signing (#8779) 2024-11-28 10:06:52 +00:00
server.go feat(v3alpha): read actions (#8357) 2024-08-12 22:32:01 +02:00
target_test.go feat(v3alpha): write actions (#8225) 2024-07-31 14:42:12 +02:00
target.go feat: action v2 signing (#8779) 2024-11-28 10:06:52 +00:00