Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-02-04 13:23:43 +01:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Notes on OAuth2 and unknown idps

Browse source
This commit is contained in:
Richard van der Hoff 2021-03-01 19:19:41 +00:00
parent ba08c9fe36
commit 6badb3b6d8
1 changed files with 10 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
proposals/2858-Multiple-SSO-Identity-Providers.md
View file

@ -110,6 +110,10 @@ For the case of backwards compatibility the existing endpoint is to remain,
and if the server supports multiple SSO IdPs it should offer the user a page
which lets them choose between the available IdP options as a fallback.
If the `idp_id` is unrecognised, the server should display some sort of error
page to the user. (A protocol whereby an error can be returned to the original
client could be a matter for a future improvement, but is out of scope for now.)
### Notes on user-interactive auth
For the case of User Interactive Auth the server would just give the standard
@ -129,6 +133,12 @@ for the server to deterministically always pick one, maybe the first option and
old clients only auth via that one but that means potentially locking users out of their
accounts.
[MSC2964](https://github.com/matrix-org/matrix-doc/pull/2964) proposes
replacing much of Matrix's authentication mechanism with OAuth2.0. If that is
adopted, then the Matrix client would not be able to specify an authentication
mechanism; rather it is left up to the server to host pages allowing the user
to choose their authentication mechanism.
### Styling information as an alternative to `brand`
The `brand` field is intended to allow clients to style "login" buttons according