Gaidaros•2d ago

Grant roles

Hi Team, I'm running zitadel on a k8s cluster using the helm chart. The app version is 4.2.0 and the chart version is 9.12.2. I have some automations for setting up the configuration on startup but I have a problem with the zitadel.authorization.v2.AuthorizationService/CreateAuthorization endpoint. I'm getting a 404 with the response looking like

  json:
    code: 5
    message: Not Found
  msg: 'Status code was 404 and not [200]: HTTP Error 404: Not Found'

  json:
    code: 5
    message: Not Found
  msg: 'Status code was 404 and not [200]: HTTP Error 404: Not Found'

I'm passing the body parameters and the headers as indicated in the documentation but it doesn't seem like it makes any difference. Creating it via the UI works but it seems like it's still using the v1 API for Add User Grant but the documentation has a deprecation notice on that API. I've added a picture of the UI page I'm talking about. Note that everything else (users, projects and roles) is created via the API, though it's still a mix of v1 and v2 APIs. Is there something I'm missing?

ZITADEL Docs

Create Authorization

ZITADEL Docs

Deprecated: Add an authorization to grant a user access to an owned or granted project.

1 Reply

Ask Inkeep•2d ago

Hi @Gaidaros, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question. Answer I wasn't able to find a direct answer, here are some relevant sources: 1. CreateAuthorization :
Documents the expected request and response for the v2 CreateAuthorization API, including required fields and error codes. 2. Problem using AuthorizationService API - {"code":5,"message":"Not Found"} :
Discussion about 404/Not Found errors with the v2 AuthorizationService endpoint, mentioning transition issues between v1 and v2 and endpoint availability in certain versions. Feel free to tag @Ask Inkeep with additional questions. Got it. Tagging @Rajat for additional help.

Grant roles

Did you find this page helpful?