Skip to content
This repository has been archived by the owner on Nov 25, 2024. It is now read-only.

Missing Admin API #1764

Open
melroy89 opened this issue Feb 12, 2021 · 7 comments
Open

Missing Admin API #1764

melroy89 opened this issue Feb 12, 2021 · 7 comments
Labels
F-Admin-API T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements.

Comments

@melroy89
Copy link
Contributor

Description:

There is no admin API implemented yet. This allows home servers to list the users on their homeserver. And list the rooms on their home servers including the complexity per room.

These Admin features are actually quite useful for homeserver owners, allowing to have better insides into the Dendrite server. And manage the server instance.

@PiotrKozimor
Copy link
Contributor

Please not that Admin API is Synapse specific and is not part of Matrix API yet: https://github.com/matrix-org/matrix-doc/issues/1411

@melroy89
Copy link
Contributor Author

Well, there is something here: https://matrix.org/docs/spec/client_server/r0.6.1#id129

But needs to be expended.

@benyanke
Copy link
Contributor

Since the admin in synapse isn't properly matrix, is there any plan to come up with a dendrite specific api? Or what is the expected way to administer a dendrite server?

@trading-peter
Copy link

I'm too wondering if more admin APIs will be added? It's a bit unfortunate that one can't disable or remove user accounts for example.

@melroy89
Copy link
Contributor Author

If you can't do basic admin operations on the dendrite server. I can't use dendrite at all. This is a major issue for me to adopt Dendrite as my default server.

@timaeos
Copy link
Contributor

timaeos commented Aug 13, 2022

Recent discussion highlighted some specific administration endpoints necessary for public administration to mitigate abuse:

  1. Purge Room (i.e. evacuate room, delete associated media from mediaapi, remove memberships)
  2. Purge User (i.e. evacuate user, delete user account, delete associated media)
  3. Force Room Membership

Based on initial discussions, the purge user administration API endpoint would likely require storing user in mediaapi which @S7evinK mentioned would likely be a part of mediaapi refactoring.

There was discussion about including purging of messages for a purged user but this could be seen as damaging to recipients of those messages.


Separately, one member of the discussion had to go through and manually purge a room from their db by:

  • Evacuating the Room
  • Deleting the relevant room from roomserver_published
  • Changing roomserver_rooms state_snapshot_nid to 0 for the relevant room
  • Deleting media from the media db
  • They also had to remove membership from syncapi_memberships due to an attempted join after evacuating the room.

This method is not recommended for use. Most administrators should wait until an administration API endpoint is added for purging a room.

@kegsay kegsay added T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements. F-Admin-API and removed feature request labels Dec 6, 2022
@onlineapps-cloud
Copy link

hi, any news about adminapi?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F-Admin-API T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements.
Projects
None yet
Development

No branches or pull requests

8 participants