You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
We have two methods from the handler that get called on each request to complete UI auth, the aptly named validate_user_via_ui_auth and a lower-level method: check_ui_auth.
All endpoints call validate_user_via_ui_auth (which calls check_ui_auth under the hood) except those that don't yet have an known requester (register and password reset) which directly call check_ui_auth.
Per matrix-org/matrix-doc#2907, the parameters of the original request to UI auth get persisted and only need to be provided once to Synapse. Unfortunately it seems that most of the endpoints which call validate_user_via_ui_auth completely disregard this and ignore the return values, using only the parameters from the most recent request.
The text was updated successfully, but these errors were encountered:
We have two methods from the handler that get called on each request to complete UI auth, the aptly named
validate_user_via_ui_auth
and a lower-level method:check_ui_auth
.All endpoints call
validate_user_via_ui_auth
(which callscheck_ui_auth
under the hood) except those that don't yet have an known requester (register and password reset) which directly callcheck_ui_auth
.Per matrix-org/matrix-doc#2907, the parameters of the original request to UI auth get persisted and only need to be provided once to Synapse. Unfortunately it seems that most of the endpoints which call
validate_user_via_ui_auth
completely disregard this and ignore the return values, using only the parameters from the most recent request.The text was updated successfully, but these errors were encountered: