MSC4191: Account management for OAuth 2.0 API#4191
Conversation
|
@mscbot fcp merge |
|
Team member @mscbot has proposed to merge this. The next step is review by the rest of the tagged people: Concerns:
Once at least 75% of reviewers approve (and there are no outstanding concerns), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for information about what commands tagged team members can give me. |
Added a reference to MSC4312 for cross-signing reset details.
Co-authored-by: Tonkku <contact@tonkku.me>
|
Per recent emails sent to oauth-ext-review on our thread, it seems possible to allow this MSC to go through without formal registration. When we get to the spec PR, we should verbosely describe the fields so we can point to them in a more complete registration application. @mscbot resolve Pending preliminary approval from oauth-ext-review to use the new names - https://mailarchive.ietf.org/arch/msg/oauth-ext-review/6RQXusbqFTy-XZCGwLSW-RIa9Dg/ |
|
🔔 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#2270 |
|
Merged 🎉 |
Rendered
Implementions:
account_management_uriandaccount_management_actions_supportedvalues in metadata. e.g. https://matrix-client.matrix.org/_matrix/client/v1/auth_metadataactionanddevice_idparametersorg.matrix.session_endorg.matrix.profile,org.matrix.sessions_listTo do:
In line with matrix-org/matrix-spec#1700, the following disclosure applies:
I am a Software Engineer at Element. This proposal was written and published as an Element employee.
SCT Stuff:
FCP tickyboxes
MSC checklist