-
Notifications
You must be signed in to change notification settings - Fork 399
MSC2966: Usage of OAuth 2.0 Dynamic Client Registration in Matrix #2966
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
MSC2966: Usage of OAuth 2.0 Dynamic Client Registration in Matrix #2966
Conversation
- 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
@mscbot concern no way for servers to gc old client IDs |
@mscbot resolve we should be able to delete unused client registrations |
This comment was marked as duplicate.
This comment was marked as duplicate.
@mscbot resolve no way for servers to gc old client IDs |
|
||
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
🔔 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#2148 |
Rendered
Dependencies:
SCT stuff:
checklist
FCP tickyboxes