UIAA for register is wrong (needs MSC)
See original GitHub issueRegistering on Conduit fails. I looked at the request jsons and it looks like it sends a /register request with just auth
and session
keys. The spec says a client should retry the original request PLUS auth and session.
https://matrix.org/docs/spec/client_server/r0.6.1#user-interactive-api-in-the-rest-api
Issue Analytics
- State:
- Created 3 years ago
- Reactions:7
- Comments:17 (15 by maintainers)
Top Results From Across the Web
2022 COMPETITION REGULATIONS - UIAA
Not every category need be provided at all international competitions. 4.3 REGISTRATION AND ISOLATION ZONE. 4.3.1 All competitors eligible ...
Read more >Street Interchange Application - UIIA
Interfaces with IANA's Global Equipment Registry (GIER) application to confirm the SCAC Code for the chassis Equipment Provider to validate the interchange ......
Read more >Issues | Conduit - Your own chat server
Conduit is a simple, fast and reliable chat server powered by Matrix. Conduit is an alternative to Synapse and tries to be lightweight...
Read more >https://www.flrules.org/gateway/readFile.asp?sid=0...
(n) F2959-14 “Standard Practice for Special Requirements for Aerial Adventure Courses.” (o) F2974-13 “Standard Guide for Auditing Amusement Rides and ...
Read more >7 Pa. Code Chapter 139A. Safety Standards For Bungee ...
Registration of bungee jumping operations. ... Association (UIAA) or, the requirements of American National Standards Institute ... (1) Two jump masters.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I made Conduit’s UIAA implementation work like synapse’s: The first request to a uiaa endpoint is saved and associated with a uiaa session. If another request to the uiaa endpoint is made with that uiaa session, we add all top level fields from the first request to the request if the field didn’t exist already.
I think we can close this issue when an MSC for this behavior is accepted
It would be great to fix this soon or even just temporarily edit the error message to say something like “registration only works with Synapse servers right now”.
Today someone was trying to setup a Dendrite server and spent hours trying to reconfigure it because they thought their server was broken but it was just this bug.