-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Follow-up to admin API to re-activate accounts #7908
Conversation
CC @dklimpel -- hopefully this meets all your feedback! |
Yes, it does. |
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.
lgtm otherwise!
Hi, sorry to hijack this thread. How would I use this feature to re-activate an account? What is the API endpoint to send the request to? It's pretty urgent as I accidentally deactivated my main-account on my homeserver while playing around with my API shellscripts. I still have another admin account to send to the API. I tried curls against endpoint addresses like this but no luck so far. Couldn't find it in the code either....didn't search extensively though.... https://my-hs.fqdn/_matrix/client/r0/admin/activate/%40${USER}%3Amy-hs.fqdn?access_token=${TOKEN}" |
Please ask support questions in #synapse:matrix.org, but you might want to check the docs first: https://github.com/matrix-org/synapse/blob/master/docs/admin_api/user_admin_api.rst#create-or-modify-account |
@clokep @anoadragon453 Hi, I reactivated a User using
but the user is still in erased_table. After an hour the entry was gone. Didn't restart the server. |
FYI, and @JOJ0 too , this is not possible. I've issued request to the support team and here is what I have received:
Bummer! |
* commit '13d77464c': Follow-up to admin API to re-activate accounts (#7908)
A follow-up to #7847 (which fixed #7220) to fix a couple of bugs, now the re-activated user is:
erased_users
table.