Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Warn if the registration flow requires a registration token #782

Closed
Half-Shot opened this issue Oct 20, 2022 · 0 comments
Closed

Warn if the registration flow requires a registration token #782

Half-Shot opened this issue Oct 20, 2022 · 0 comments

Comments

@Half-Shot
Copy link
Member

Your use case

Homeserver admins can configure their homeserver to require a registration token upon registration, a shared secret token that only allows some users to register. However, since Element isn't "aware" of this feature yet it doesn't prompt for the token on registration. Rather, it accepts the users registration details but then redirects them to the homeserver to enter the token.

This is frustrating for users who attempt to sign up to a host, only to be surprised by an additional requirement. Element is aware of all the registration flows, and could warn about future flows. My suggestion would be to implement a simple warning box when Element is going to redirect you to complete additional flows.

Have you considered any alternatives?

Implement element-hq/element-web#7275, which should hopefully implicitly warn. Given the current progress however, it seems like a intermediary PR to warn might be appropriate.

Additional context

As an example, a homeserver can be configured to have a set of registration flows like:

{
    "session": "qeLMBdbowXJQqtCRvdlfSEID",
    "flows": [
        {
            "stages": [
                "m.login.registration_token",
                "m.login.terms",
                "m.login.email.identity"
            ]
        },
        {
            "stages": [
                "m.login.terms",
                "m.login.registration_token"
            ]
        }
    ],
    "params": {
        "m.login.terms": {
            "policies": {
                "privacy_policy": {
                    "version": "1.0",
                    "en": {
                        "name": "Privacy Policy",
                        "url": "https://foobar/_matrix/consent?v=1.0"
                    }
                }
            }
        }
    }
}
@t3chguy t3chguy transferred this issue from element-hq/element-web Oct 20, 2022
@element-hq element-hq locked and limited conversation to collaborators Oct 20, 2022
@t3chguy t3chguy converted this issue into discussion #783 Oct 20, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

1 participant