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

Ability to disable IS via blank URL regressed #10086

Closed
jryans opened this issue Jun 18, 2019 · 5 comments
Closed

Ability to disable IS via blank URL regressed #10086

jryans opened this issue Jun 18, 2019 · 5 comments
Assignees

Comments

@jryans
Copy link
Collaborator

jryans commented Jun 18, 2019

It has historically been possible to set the default_is_url to a blank URL and disable associated functionality. Doing so may have thrown various errors.

For this issue, we want to limit scope to repairing this regression only. The larger work of smoothly disabling all IS functionality is left to #5921.

@jryans
Copy link
Collaborator Author

jryans commented Jun 18, 2019

Hmm, as best as I can tell, we default to https://vector.im when default_is_url is blank going back to at least Riot 1.0.0, but possibly further back as well. @turt2live, do have more details about this regression?

@turt2live
Copy link
Member

#5921 was meant to track the regression - closing in favour of that.

@jryans
Copy link
Collaborator Author

jryans commented Jun 18, 2019

@turt2live I guess I am puzzled that we're saying #5921 tracks a regression if it was filed in Jan 2018... I assumed it was describing a future feature request that we've never implemented so far.

@turt2live
Copy link
Member

The longer story is that 5921 was created as a result of a conversation in #riot where several people were having trouble disabling the identity server. In their particular use case, they wanted to be absolutely sure that the identity server would never be contacted for corporate policy reasons, however it was found at that time that the default_is_url: "" trick didn't work anymore. The idea behind opening the issue (which was through the github bot, hence the terseness) was that by now Riot would have added a way to disable the identity server, therefore fixing the regression and introducing a new feature.

@jryans
Copy link
Collaborator Author

jryans commented Jun 18, 2019

Okay, thanks for the additional detail! I think I got confused by the word "regression" and assumed it was a recent change, but in reality it hasn't worked for a long time.

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