Overview - Zitadel/zitadel

zitadel/zitadel

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
fix/console-rm-role-assignment-in-profile
a5122eb4 feat: rt recovery code check (#11848) # Which Problems Are Solved Adding recovery code check step required for the CreateSession RT implementation. # How the Problems Are Solved - Introduce `RecoveryCodeCheckCommand` (validate/execute/events) for session creation checks - Add unit tests # Additional Changes - refactor password-check code to reuse a shared lockout-policy helper - add some missing error translations in `internal/static/i18n/en.yaml` # Additional Context - Related to https://github.com/zitadel/zitadel/issues/11035 --------- Co-authored-by: Silvan <27845747+adlerhurst@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
13 days ago by Gayathri V...
Succeeded
fix/console-rm-role-assignment-in-profile
a5122eb4 Merge 30269476f162128696e7ebb74ad209489e400959 into c6386cb8073806becaf4d65619491a2a7a4a783e
13 days ago by Ramon
Failed
fix/console-rm-role-assignment-in-profile
13 days ago
Succeeded
fix/console-rm-role-assignment-in-profile
103b04e4 feat(telemetry): unify request details (#11509) # Which Problems Are Solved In the "new" structured logging, request details were added in different middlewares, such as request, instance and user IDs. This meant the the upstream request logging middleware did not have access to metadata that got added later, resulting in incomplete logs. Furthermore it was not possible to correlate an API error response to log output. # How the Problems Are Solved A mutable request details object is added to the context early on. When the api authz function run, the instance and user IDs are added to this object as they become available. Every logline emitted after this (time-wise) will then all contain these details under the `request` log group. <details> <summary>example output in JSON</summary> ```json { "time": "2026-03-13T19:21:20.890428806Z", "level": "INFO", "source": { "function": "github.com/zitadel/zitadel/internal/api/grpc/server/connect_middleware.LogHandler.func1.1", "file": "/workspaces/zitadel/internal/api/grpc/server/connect_middleware/log_interceptor.go", "line": 34 }, "msg": "request served", "request": { "id": "d6q67c04vtjmi77cbbpg", "instance_host": "localhost:8080", "instance_id": "362349751439458307", "user_id": "362349751440048131" }, "TraceID": "a9e0fee3522224f3583bbdcda737f4b4", "SpanID": "a563056eee36920a", "stream": "request", "version": "2026-03-13T19:20:59Z", "protocol": "connect", "service": "zitadel.user.v2.UserService", "http_method": "POST", "path": "/zitadel.user.v2.UserService/ListUsers", "code": "code_0", "duration": 12254350 } ``` </details> Request IDs are now also returned with a response header or metadata. Depending on the protocol: - HTTP calls always return the request ID as header, regardless of status - gRPC calls always return the request ID as header, even if there was an error - connect RPC calls returns the request ID as header on success, trailer in case of error. This is because header must be set on the response object, which is nil in case of error. When there is an error, metadata can be added which are then sent as trailers. # Additional Changes - Use the existing call duration middleware for both request ID and logging for a consistent request start timestamp in all layers. - Upgrade sloggcp for some fixes (notably TraceID) - Modify the NoCache middleware so it uses `SetHeaders` instead of `SendHeaders`. The latter prevented any other handler from setting headers, including the new request ID middleware. # Additional Context Follow up on demo of: - https://github.com/zitadel/zitadel/pull/11159 - https://github.com/zitadel/zitadel/pull/11435 - backport to v4 --------- Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com> Co-authored-by: muhlemmer <5411563+muhlemmer@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Co-authored-by: Marco A. <marco@zitadel.com>
18 days ago by Tim Möhlmann
Succeeded
fix/console-rm-role-assignment-in-profile
103b04e4 Merge c55a4730525496c958a18a5201aeef8bd29d1d02 into 997aa607c474f5d09a84f425cd11620ec7c356cd
18 days ago by Ramon
Succeeded
fix/console-rm-role-assignment-in-profile
18 days ago
Succeeded
fix/console-rm-role-assignment-in-profile
cfb345a6 fix: delete role assignment in profile
19 days ago by conblem
Succeeded
fix/console-rm-role-assignment-in-profile
cfb345a6 Merge 2e0ca4ebf58717a3258591cf2d1409a8981e1014 into f138082b64513955466e8dddc8de2a5a1e4e6c8e
19 days ago by Ramon
Succeeded
fix/console-rm-role-assignment-in-profile
19 days ago