zitadel/internal/api/grpc/server
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
..
middleware feat: action v2 signing (#8779) 2024-11-28 10:06:52 +00:00
gateway.go feat: trusted (instance) domains (#8369) 2024-07-31 18:00:38 +03:00
probes_test.go refactor: rename package errors to zerrors (#7039) 2023-12-08 15:30:55 +01:00
probes.go refactor: rename package errors to zerrors (#7039) 2023-12-08 15:30:55 +01:00
server.go chore(tests): use a coverage server binary (#8407) 2024-09-06 14:47:57 +02:00