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

Mjolnir is incompatible with homeservers running MAS #566

Open
Thanhphan1147 opened this issue Jan 9, 2025 · 1 comment
Open

Mjolnir is incompatible with homeservers running MAS #566

Thanhphan1147 opened this issue Jan 9, 2025 · 1 comment

Comments

@Thanhphan1147
Copy link

Hello, with MAS taking over the responsibility of managing users and tokens. A number of synapse admin API is disabled when MAS (msc3861) is activated as mentioned here:

The following admin APIs are disabled:

/users/:user_id/admin
/users/:user_id/login
/registration_tokens
/registration_tokens/new
/registration_tokens/:token
/reset_password
/register

From what I understand mjolnir calls the /users/:user_id/admin API which serves as a precondition for most commands as shown here and since this API is disabled when MAS is activated, we can't run most mjolnir commands.

If this is indeed the case then can I ask if there are any plans to make mjolnir compatible with MAS? I also think that relying on the synapse admin API is unnecessary as any API requests with insufficient permission will return a 403 which we can check for.

Thank you!

@H-Shay
Copy link
Contributor

H-Shay commented Jan 9, 2025

Yes, we will be doing work to make mjolnir compatible with both MAS and non-MAS using Synapse setups.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants