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

Remove unspecified 'success' parameter from requestToken responses #302

Merged
merged 1 commit into from
Jun 22, 2020

Conversation

babolivier
Copy link
Contributor

It doesn't look like it's ever been a thing in the spec, and we don't seem to be checking this parameter in Synapse.

It can be an issue to have this parameter around for servers that have the setting from matrix-org/synapse#7315 turned on and are delegating emails to an IS, because then you can figure out whether the server is lying to you just by checking on whether there's a success in the response.

@babolivier babolivier requested a review from a team June 17, 2020 15:45
@babolivier babolivier force-pushed the babolivier/request_token_success branch from 11beb84 to fd385c5 Compare June 17, 2020 15:46
@anoadragon453
Copy link
Member

anoadragon453 commented Jun 17, 2020

My personal theory is that this was just an accidental inclusion due to success being a parameter on the /submitToken endpoint: https://matrix.org/docs/spec/identity_service/latest#post-matrix-identity-v2-validate-email-submittoken

Ideally we would poke a tendril out and ask if any other clients/servers are using this before we remove it.

Edit: I've asked in #matrix-client-developers:matrix.org and #homeservers-dev:matrix.org.

@clokep
Copy link
Member

clokep commented Jun 22, 2020

Edit: I've asked in #matrix-client-developers:matrix.org and #homeservers-dev:matrix.org.

Is this waiting for a response or just someone to review the code (or are you already handling that @anoadragon453 ?)

@babolivier
Copy link
Contributor Author

afaict folks in these rooms have said that they weren't using this parameter so I think this is just waiting for a review.

@anoadragon453
Copy link
Member

Community people have already clarified that it's not being used in both clients nor servers, and it's been some time since we've asked now, so I think it's fine from that perspective.

I forget if we asked Riot people though?

@babolivier
Copy link
Contributor Author

I forget if we asked Riot people though?

I don't think we have, I'm asking internally rn.

@jryans
Copy link

jryans commented Jun 22, 2020

It looks fine for Riot Web at least, we don't use this parameter.

@babolivier
Copy link
Contributor Author

The mobile apps' devs shared that it looks fine from their pov as well.

Copy link
Member

@anoadragon453 anoadragon453 left a comment

Choose a reason for hiding this comment

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

Seems that this won't break anything, and it is indeed not in the spec.

Copy link
Member

@anoadragon453 anoadragon453 left a comment

Choose a reason for hiding this comment

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

Oh, actually, last thing. Could you specify when this was introduced in the newsfile? :)

@babolivier
Copy link
Contributor Author

Oh, actually, last thing. Could you specify when this was introduced in the newsfile? :)

It's always been there apparently, not sure it makes much sense to say so in the changelog.

@babolivier babolivier merged commit 052fdb3 into master Jun 22, 2020
@babolivier babolivier deleted the babolivier/request_token_success branch June 22, 2020 16:11
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

Successfully merging this pull request may close these issues.

4 participants