[management] Feature - Migration to Zitadel v2 API #2994
+20
−31
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
|
remipcomaite
changed the title
|
Thank you for the contribution @remipcomaite |
|
Hello @braginini , The code is not backwards compatible because V1 of the API will be deprecated in the long term. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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".
To be able to authenticate users from multiple organizations, you must add the User service in each organization with the "Org User Manager" role as described in the Netbird documentation.
Issue ticket number and link
Checklist