Sensible error message for homeservers with no supported registration methods

[MomentQYC]

Steps to reproduce

Register

Outcome

What did you expect?

Complete the process and register successfully.

What happened instead?

Show "No appropriate authentication flow found" Error. The 2nd image is taken from a synapse homeserver (1.73.0)

Operating system

Zorin OS 16.2 Pro (Ubuntu 20.04)

Browser information

Edge 108

URL for webapp

Dec. 9, 2022 Clone from GitHub

Will you send logs?

No

[MomentQYC]

Use reCaptcha and third-party login Email required to register

[dbkr]

This is likely to be that Element Call isn't compatible with your homeserver's registration methods. If your homeserver requires an email address to register, element call can't (currently?) use it.

[MomentQYC]

This is likely to be that Element Call isn't compatible with your homeserver's registration methods. If your homeserver requires an email address to register, element call can't (currently?) use it.

So I think this issue can be turned into a feature request

[dbkr]

You're welcome to do so, although I suspect this might fall into the bucket of, "just use Element Web" - the product folks can confirm though.

[t3hmrman]

I just ran into this and wanted to note -- what if Element Call exposed a token field so that people could supply that during guest account creation time?

As far as I can tell there are ~4 ways to register:

• Captcha (requires Recaptcha, not a huge fan)
• Email (full registration seems like a lot for )
• MSISDN
• Token

Token is the most attractive to me out of those options as far as ease of use and effectiveness.

Having at least another input to provide a token would open up the path for manual/automated meeting invites with strangers, i.e.:

• generate a token via the admin API
• include token in email or calendar event w/ meeting link).

[dbkr]

For now, I'm going to say the first thing we should do here is make EC display a proper error message. We can discuss separately whether it's within EC's product remit to support more registration methods.

[SnoutBug]

I am also in favor of some form of support for token based registration. I think that it is not uncommon for users hosting their own matrix synapse instance to have token based registration enabled. As far as I am aware, in most setup guides, token based registration is advertised in contrast to all other registration methods. I can see this being also super useful for a business environment, where we could just give out the URL for a call on Element Call together with the registration token which enables our bp to get in touch with us without having to a. create an account themselves, b. us having to create an account for them or c. us having to open all doors to our matrix instance for the sake of simplicity. Alternatively, I could also see Element Call making use of guest access which is exactly for cases like this.