-
Notifications
You must be signed in to change notification settings - Fork 55
New admin API endpoint to reactivate users & align what lock/unlock/deactivate does in the admin API #4768
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
Conversation
Deploying matrix-authentication-service-docs with
|
Latest commit: |
8ac2770
|
Status: | ✅ Deploy successful! |
Preview URL: | https://9d9449c8.matrix-authentication-service-docs.pages.dev |
Branch Preview URL: | https://af-rest-reactivate.matrix-authentication-service-docs.pages.dev |
Marking this as draft until it makes use of #4775 to test the updating of the |
9e89708
to
4c40c25
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Almost there! I just want to avoid changes in behaviour on the GraphQL API, as it's used in our tools that haven't migrated to the admin API yet… unless you want to also fix those tools :D
- Allow the admin API to deactivate a user without locking it, and to unlock a user without reactivating it. - Make unlock-and-reactivate flows unset the "deactivated_at" timestamp. - Revert adding an "unlock" parameter on `ReactivateUserJob`, as the option is used only by the admin API which doesn't use a job.
Unify the admin API, CLI, and GraphQL API in not having the unlock command also reactivate, or the deactivate command also lock. Still let the unlock command of the CLI and GraphQL API to also reactivate the target user, albeit as a non-default option.
Unlike the CLI and admin API, leave the behaviour of the GraphQL's unlock handler unchanged from before, so as to not break internal tooling that depends on it. Also update its documentation description to make note of the fact that it reactivates in addition to unlocks.
43806cd
to
8ac2770
Compare
Fixes #4740
This changes the lock/unlock/deactivate endpoints to: