Skip to content

Conversation

@meson800
Copy link
Contributor

Currently, the homeserver login flows are checked even if MSC4190 is enabled. However, the flows variable is unused when MSC4190 is enabled.

This is an unnecessary network call, and also e.g. requires a reverse proxy soley for this purpose if bridges would otherwise directly connect to a homeserver that is delegating OIDC authentication.

Closes #177.

Testing, linting, etc

  • This change didn't have the test suite run, since locally my CMake version differs, so the olm package build fails locally, etc.
  • I ran black and the pre-commit hooks from the Github actions.
  • This bridge was tested on my homeserver, using my custom build of mautrix-googlechat that uses mautrix-python from this commit with MSC4190 support. Docker container build here. Messages flow bidirectionally, double puppeting works, etc.

Currently, the homeserver login flows are checked even if MSC4190 is
enabled. However, the `flows` variable is unused when MSC4190 is
enabled.

This is an unnecessary network call, and also e.g. requires a
reverse proxy soley for this purpose if bridges would otherwise
directly connect to a homeserver that is delegating OIDC authentication.

Closes mautrix#177.
@Sharparam
Copy link

Sharparam commented Aug 11, 2025

This will also close mautrix/telegram#1020 (which is currently closed in error).

Copy link

@Sharparam Sharparam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've tested the same changes on my server and they work as expected.

@tulir tulir merged commit 0349445 into mautrix:master Aug 11, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

MSC4190 login fails with MAS, due to unnecessarily checking for login flows

3 participants