MSC2966: Usage of OAuth 2.0 Dynamic Client Registration in Matrix#2966
Merged
turt2live merged 35 commits intomatrix-org:mainfrom Apr 5, 2025
Merged
Conversation
turt2live
changed the title
turt2live
added
kind:feature
9 tasks
richvdh
reviewed
Feb 4, 2021
richvdh
reviewed
Feb 13, 2021
turt2live
added
the
needs-implementation
39 tasks
deepbluev7
reviewed
Feb 24, 2023
zecakeh
reviewed
Aug 4, 2023
39 tasks
- makes some metadata optional - better explain how each metadata field is used - better explain what the restrictions on redirect_uris are - remove the signed metadata part - mention the client metadata JSON document alternative
sandhose
changed the title
mscbot
removed
the
unresolved-concerns
dbkr
reviewed
Mar 31, 2025
|
|
||
| This proposal is part of the broader [MSC3861: Next-generation auth for Matrix, based on OAuth 2.0/OIDC][MSC3861]. | ||
|
|
||
| This MSC specifies how Matrix clients SHOULD leverage the OAuth 2.0 Dynamic Client Registration Protocol ([RFC 7591](https://tools.ietf.org/html/rfc7591)) to register themselves before initiating an authorization flow. |
Member
There was a problem hiding this comment.
Not to be a stickler, but I think having this 'should' in formal capitals technically implies the whole MSC is optional, which is probably not what you want.
Collaborator
|
🔔 This is now entering its final comment period, as per the review above. 🔔 |
mscbot
added
final-comment-period
Collaborator
|
The final comment period, with a disposition to merge, as per the review above, is now complete. |
mscbot
added
finished-final-comment-period
and removed
disposition-merge
final-comment-period
turt2live
added
spec-pr-missing
Contributor
|
spec PR: matrix-org/matrix-spec#2148 |
tulir
added
spec-pr-in-review
turt2live
moved this from Requires spec writing
to Done to some definition
in Spec Core Team Workflow
turt2live
moved this from Done to some definition
to Requires spec PR review
in Spec Core Team Workflow
Member
Merged! 🎉 |
richvdh
added
merged
turt2live
moved this from Requires spec PR review
to Done to some definition
in Spec Core Team Workflow
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
17 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rendered
Dependencies:
SCT stuff:
checklist
FCP tickyboxes