zitadel/cmd
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
..
admin chore: test server for direct resource access 2023-04-24 20:40:31 +03:00
build fix: allow version to be overwritten by build again (#4656) 2022-11-07 09:50:44 +00:00
encryption feat: action v2 signing (#8779) 2024-11-28 10:06:52 +00:00
hooks feat: support whole config as env (#6336) 2024-02-16 16:04:42 +00:00
initialise feat(v3alpha): web key resource (#8262) 2024-08-14 14:18:14 +00:00
key feat: api v2beta to api v2 (#8283) 2024-07-26 22:39:55 +02:00
mirror feat: action v2 signing (#8779) 2024-11-28 10:06:52 +00:00
ready feat(v3alpha): web key resource (#8262) 2024-08-14 14:18:14 +00:00
setup feat: action v2 signing (#8779) 2024-11-28 10:06:52 +00:00
start feat: action v2 signing (#8779) 2024-11-28 10:06:52 +00:00
tls fix: enable env vars in setup steps (and deprecate admin subcommand) (#3871) 2022-06-27 10:32:34 +00:00
defaults.yaml feat: action v2 signing (#8779) 2024-11-28 10:06:52 +00:00
zitadel.go fix(mirror): read config correctly (#8330) 2024-07-18 14:00:58 +00:00