zitadel/cmd/start
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
..
config_test.go fix: correctly check denied domains and ips for actions (#8810) 2024-10-22 16:16:44 +02:00
config.go feat(notification): use event worker pool (#8962) 2024-11-27 15:01:17 +00:00
flags.go refactor(fmt): run gci on complete project (#7557) 2024-04-03 10:43:43 +00:00
start_from_init.go feat(cmd): mirror (#7004) 2024-05-30 09:35:30 +00:00
start_from_setup.go feat(cmd): mirror (#7004) 2024-05-30 09:35:30 +00:00
start.go feat: action v2 signing (#8779) 2024-11-28 10:06:52 +00:00