-
Notifications
You must be signed in to change notification settings - Fork 423
MSC4198: Usage of OIDC login_hint #4198
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
base: main
Are you sure you want to change the base?
Conversation
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.
Implementation requirements:
- Client
- Authentication service (I think?)
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.
Authentication service
well... technically just "server"? nobody is prescribing the auth to happen in an extra microservice, right?
noelportillo
left a comment
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.
First thing that came out
hughns
left a comment
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.
I suggest:
- Updating to reflect that OAuth 2.0 API now exists in the spec
- Making it explicit that this is an optional parameter for the Authorization code grant
- Propose that that the
login_hintcan also be added to the MSC4191 account management URL query parameters (perhaps prefixed asorg.matrix.msc4198.login_hint)
By using RFC2119 keywords and reiterating that the parameter is optional in the usage section
Rendered
Implementations:
login_hintas per MSC4198 element-hq/matrix-authentication-service#3343