# Which Problems Are Solved
The commands for the resource based v2beta AuthorizationService API are
added.
Authorizations, previously knows as user grants, give a user in a
specific organization and project context roles.
The project can be owned or granted.
The given roles can be used to restrict access within the projects
applications.
The commands for the resource based v2beta InteralPermissionService API
are added.
Administrators, previously knows as memberships, give a user in a
specific organization and project context roles.
The project can be owned or granted.
The give roles give the user permissions to manage different resources
in Zitadel.
API definitions from https://github.com/zitadel/zitadel/issues/9165 are
implemented.
Contains endpoints for user metadata.
# How the Problems Are Solved
### New Methods
- CreateAuthorization
- UpdateAuthorization
- DeleteAuthorization
- ActivateAuthorization
- DeactivateAuthorization
- ListAuthorizations
- CreateAdministrator
- UpdateAdministrator
- DeleteAdministrator
- ListAdministrators
- SetUserMetadata to set metadata on a user
- DeleteUserMetadata to delete metadata on a user
- ListUserMetadata to query for metadata of a user
## Deprecated Methods
### v1.ManagementService
- GetUserGrantByID
- ListUserGrants
- AddUserGrant
- UpdateUserGrant
- DeactivateUserGrant
- ReactivateUserGrant
- RemoveUserGrant
- BulkRemoveUserGrant
### v1.AuthService
- ListMyUserGrants
- ListMyProjectPermissions
# Additional Changes
- Permission checks for metadata functionality on query and command side
- correct existence checks for resources, for example you can only be an
administrator on an existing project
- combined all member tables to singular query for the administrators
- add permission checks for command an query side functionality
- combined functions on command side where necessary for easier
maintainability
# Additional Context
Closes#9165
---------
Co-authored-by: Elio Bischof <elio@zitadel.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Livio Spring <livio.a@gmail.com>
# Which Problems Are Solved
This fix adds tracing spans to all V1 API import related functions. This
is to troubleshoot import related performance issues reported to us.
# How the Problems Are Solved
Add a tracing span to `api/grpc/admin/import.go` and all related
functions that are called in the `command` package.
# Additional Changes
- none
# Additional Context
- Reported by internal communication
* feat: user meta data events
* feat: user meta data set tests
* feat: user meta data tests
* feat: user meta data in protos
* feat: user meta data command api
* feat: user meta data query side
* feat: proto correct order, fix handlers
* feat: proto correct order
* feat: fixes of pr comments
* feat: fixes of pr comments
* feat: value as byte array
* feat: metadata feature
* Update internal/auth/repository/eventsourcing/handler/meta_data.go
Co-authored-by: Silvan <silvan.reusser@gmail.com>
* Update internal/command/user_meta_data.go
Co-authored-by: Silvan <silvan.reusser@gmail.com>
* Update proto/zitadel/metadata.proto
Co-authored-by: Silvan <silvan.reusser@gmail.com>
* Update proto/zitadel/metadata.proto
Co-authored-by: Silvan <silvan.reusser@gmail.com>
* fix: rename metadata files and table
* fix: rename meta data to metadat in protos
* Update internal/domain/metadata.go
Co-authored-by: Silvan <silvan.reusser@gmail.com>
* fix: rename vars
* fix: rebiuld docs
* Update internal/iam/repository/view/metadata_view.go
Co-authored-by: Silvan <silvan.reusser@gmail.com>
Co-authored-by: Silvan <silvan.reusser@gmail.com>
