From 21baec924ae9923c883e2d1c4e9fbab53da2adf0 Mon Sep 17 00:00:00 2001
From: Livio Spring <livio.a@gmail.com>
Date: Fri, 13 Dec 2024 11:24:14 +0100
Subject: [PATCH] fix(api): map REST request body in user invite requests
 (#9054)

# Which Problems Are Solved

The `CreateInviteCode` and `VerifyInviteCode` methods missed the body
mapping.

# How the Problems Are Solved

Added the mapping.

# Additional Changes

None

# Additional Context

Noticed during internal login UI tests using REST

(cherry picked from commit fd70a7de5fdb0c0f315847f0ed0be7bb283ce9f6)
---
 proto/zitadel/user/v2/user_service.proto | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/proto/zitadel/user/v2/user_service.proto b/proto/zitadel/user/v2/user_service.proto
index 47707fef4f..0276e51c8c 100644
--- a/proto/zitadel/user/v2/user_service.proto
+++ b/proto/zitadel/user/v2/user_service.proto
@@ -1091,6 +1091,7 @@ service UserService {
   rpc CreateInviteCode (CreateInviteCodeRequest) returns (CreateInviteCodeResponse) {
     option (google.api.http) = {
       post: "/v2/users/{user_id}/invite_code"
+      body: "*"
     };
 
     option (zitadel.protoc_gen_zitadel.v2.options) = {
@@ -1140,6 +1141,7 @@ service UserService {
   rpc VerifyInviteCode (VerifyInviteCodeRequest) returns (VerifyInviteCodeResponse) {
     option (google.api.http) = {
       post: "/v2/users/{user_id}/invite_code/verify"
+      body: "*"
     };
 
     option (zitadel.protoc_gen_zitadel.v2.options) = {