forked from continuwuation/continuwuity
The appservice branch of update_device_route (MSC4190 device creation) generated a random device ID instead of using the one from the request path, and dropped the requested display name. The PUT returned 200, but the device the appservice asked for never existed, so every subsequent request masquerading as that device failed with M_FORBIDDEN and one orphaned random-ID device was left behind per attempt. This made encrypted mautrix (bridgev2) bridges unable to start on OIDC-enabled servers, where MSC4190 is the only available device creation mechanism: /keys/upload failed on first start and /keys/query on every restart. Combined with the pre-1f5e178c3f behaviour (400 "Token conflicts with an existing appservice token"), MSC4190 device creation has never worked end-to-end in any release. Create the device under the requested ID and forward the requested display name. |
||
|---|---|---|
| .. | ||
| +8b3a57647.bugfix.md | ||
| +30d4369c.bugfix.md | ||
| +39fcec3a.bugfix.md | ||
| +88fbb987.bugfix.md | ||
| +724f9fed.bugfix.md | ||
| +df2f1c78.bugfix.md | ||
| 1965.bugfix | ||
| 1984.bugfix | ||
| 1987.bugfix | ||
| 1994.bugfix.md | ||
| 1999.doc | ||
| 2006.bugfix | ||
| 2015.bugfix.md | ||
| fix-federation-signature.bugfix | ||