zitadel/cmd/mirror
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
..
auth.go feat(cmd): mirror (#7004) 2024-05-30 09:35:30 +00:00
config.go feat(v3alpha): web key resource (#8262) 2024-08-14 14:18:14 +00:00
defaults.yaml feat(cmd): mirror (#7004) 2024-05-30 09:35:30 +00:00
event_store.go fix(eventstore): revert precise decimal (#8527) (#8679) 2024-09-24 18:43:29 +02:00
event.go fix(eventstore): revert precise decimal (#8527) (#8679) 2024-09-24 18:43:29 +02:00
mirror.go fix(mirror): read config correctly (#8330) 2024-07-18 14:00:58 +00:00
projections.go feat: action v2 signing (#8779) 2024-11-28 10:06:52 +00:00
system.go feat(cmd): mirror (#7004) 2024-05-30 09:35:30 +00:00
verify.go fix(mirror): Fix instance_id check for tables without (#8852) 2024-11-12 16:03:41 +00:00