[management] Feature - Migration to Zitadel v2 API

[remipcomaite]

Describe your changes

Hello,

I propose a PR to migrate to Zitadel API v2.

This allows to authenticate users from different organizations.

The endpoint for the management API changes from "/management/v1" to "/v2".

Issue ticket number and link

Checklist

• Is it a bug fix
• Is a typo/documentation fix
• Is a feature enhancement
• It is a refactor
• Created tests that fail without the change (if possible)
• Extended the README / documentation, if necessary

[CLAassistant]

All committers have signed the CLA.

[braginini]

Thank you for the contribution @remipcomaite
Is this backwards compatible with the previous version?

[remipcomaite]

Hello @braginini ,

The code is not backwards compatible because V1 of the API will be deprecated in the long term.
I changed the endpoints and some properties to match the API calls with V2.

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (1)

management/server/idp/zitadel.go:73

• The variable name 'ID' has been changed to 'userId'. Ensure that this renaming is consistently applied throughout the codebase to avoid confusion.

ID: string `json:"userId"`

[mlsmaycon]

@remipcomaite when was v1 support removed from Zitadel?

[remipcomaite]

@remipcomaite when was v1 support removed from Zitadel?

@mlsmaycon I don't know but v1 (service-based) and v2 (resource-based) are GA.
The v3 version of the API is in "Preview".

https://zitadel.com/docs/apis/introduction

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[mlsmaycon]

@remipcomaite when was v1 support removed from Zitadel?

@mlsmaycon I don't know but v1 (service-based) and v2 (resource-based) are GA. The v3 version of the API is in "Preview".

https://zitadel.com/docs/apis/introduction

Thanks for checking @remipcomaite. I've asked in Zitadel's community discord, and it appears that they don't have a plan to deprecate the API yet. But the notification gives us an idea of the overall intentions.

With that said, the problem with dropping V1 support on our end is that self-hosted users would have to upgrade their Zitadel's servers before updating NetBird's management service, and that will generate Github and Slack requests for assistance, which we can't provide.

An alternative to that is to make v2 support optional on our side and keep v1 support for those users.

That could be an IDP extra configuration, which, by default, uses V1, but we set our deployment scripts and guides to use V2. What do you think?

[remipcomaite]

That could be an IDP extra configuration, which, by default, uses V1, but we set our deployment scripts and guides to use V2. What do you think?

Yes, I think it's the best option.