-
Notifications
You must be signed in to change notification settings - Fork 385
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
MSC3012: Post-registration terms of service API #3012
base: old_master
Are you sure you want to change the base?
Conversation
6. The homeserver logs the user in by generating a token and returning it to the client as per | ||
the specification. | ||
|
||
This process is chosen to begin introducing the UI auth mechanism to login without breaking clients. |
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.
#2835 switches to full UIA directly and does not break login with existing clients. Special-casing terms seems unneeded?
In addition, the homeserver should not prevent the use of the special "terms acceptance" API | ||
described in the next section. | ||
|
||
### Terms acceptance API |
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.
there should also be an (unauthenticated) endpoint to get the current terms, mirroring the identity server approach. Optional authentication for scoping.
Rendered