Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Command Side for Users with User Schemas (Updates) #7898

Open
10 tasks
Tracked by #6433
hifabienne opened this issue May 3, 2024 · 1 comment
Open
10 tasks
Tracked by #6433

Command Side for Users with User Schemas (Updates) #7898

hifabienne opened this issue May 3, 2024 · 1 comment

Comments

@hifabienne
Copy link
Member

hifabienne commented May 3, 2024

As a ZITADEL Administrator I want to be able to update users and their states that apply to a predefined user schema, so I am able to ensure that my user data is consistent and applies to my standards.

Acceptance Criteria

  • Feature is behind a feature flag
  • UpdateUser: changes an existing user. The type of a user cannot be changed
  • LockUser: changes the state of the user to locked
  • UnlockUser: changes the state of the user to active after it was locked
  • DeactivateUser: changes the state of the user to inactive
  • ReactivateUser: changes the state of the user to active after it was locked
  • the user data is filled according to the predefined user schema
  • As an admin I am able to change all fields that are defined as writeable by admin
  • As an end user I am not able to change fields that are only writeable by an admin
  • if user doesn't match the userschema, human readable error message is shown

Additional Information

User Object

  • id: unchangeble, unique identifier of the system
  • schema:
    • type: schema type of the user (e.g. human/machine)
    • revision: read only, revision of the schema the user was stored the last time (e.g. 4)
  • authenticators: list of possibilites how a user can authenticate itself. there can be multiple authenticators of the same type
  • contact: email and phone of the user if provided
  • state: one of Active, Inactive, Locked, Deleted
  • data/profile/traits: custom fields of a user based on the type (whats the best name for this?)
@hifabienne
Copy link
Member Author

hifabienne commented May 3, 2024

@eliobischof @stebenz as discussed I split the issue into create/delete and update functions.
Can you please estimate this?

Relates:
#7308

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 📝 Prioritized Product Backlog
Development

No branches or pull requests

3 participants