Skip to content

MSC2284: Making the identity server optional during discovery #2284

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Nov 18, 2019
Merged

MSC2284: Making the identity server optional during discovery #2284

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
738fa68
Proposal to make the identity server optional during discovery
turt2live Sep 6, 2019
6baeb6c
Assign number
turt2live Sep 6, 2019
dcbdb94
Add explanation
turt2live Nov 8, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Add explanation
  • Loading branch information
@turt2live
turt2live authored Nov 8, 2019
commit dcbdb94693edcff28efbb813302c90248258cbcc
4 changes: 3 additions & 1 deletion proposals/2284-optional-identity-server-discovery.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,9 @@

Currently the specification requires that clients `FAIL_ERROR` (hard failure - do not continue)
when the `.well-known` file for `m.identity_server` points to somewhere invalid or is invalid
itself.
itself. This can cause problems for clients if they either don't need an identity server to
function (and are forced to validate it anyways) or the client ends up having to disable all
their login UX because the identity server is misconfigured/down.

This proposal aims to change that by allowing clients to make a conscious decision to continue
with the invalid identity server configuration, provided the homeserver configuration is valid.
Expand Down