-
Notifications
You must be signed in to change notification settings - Fork 418
MSC3824: OAuth 2.0 API aware clients #3824
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
Conversation
This comment was marked as duplicate.
This comment was marked as duplicate.
|
(implementation nor the MSC have been sufficiently reviewed to remove the label - when someone on the SCT is comfortable with where things are at, they'll remove the label. Personally, I haven't gotten as far as deciding if I'm comfortable with it 😅) |
|
I think an important part of this would also be to be able to advertise what actions are available with each login method, e.g. {
"flows": [{
"type": "m.login.password",
"actions": ["login"],
}, {
"type": "m.login.sso",
"actions": ["login", "register"]
}]
}This would allow clients to properly display what's really available for each login method |
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
|
Matrix Authentication Service support within it's compatibility layer is in matrix-org/matrix-authentication-service#221 |
Co-authored-by: Hubert Chathi <hubertc@matrix.org>
|
🔔 This is now entering its final comment period, as per the review above. 🔔 |
|
The final comment period, with a disposition to merge, as per the review above, is now complete. |
|
Spec PR: matrix-org/matrix-spec#2272 |
Rendered
Dependencies:
Servers
Clients
SCT Stuff:
FCP tickyboxes
MSC checklist