Tulir Asokan
Tulir Asokan
This is implemented in Synapse and most mautrix bridges. It'd be nice if it was in the same spec release as the rest of next-gen auth @mscbot fcp merge
@mscbot concern checklist not complete
@mscbot resolve checklist not complete
@mscbot concern This actually depends on MSC3202 device masquerading to be useful
I've made some more changes to the MSC: * The wording has been updated as OAuth2 is in the spec now. * The registration flag will now be used even...
I was keeping the MSC3202 concern to wait for dependencies, but I guess blocking on the checklist is more accurate (especially now that the dependency is MSC4326, not MSC3202) so...
MSC4326's FCP finished: @mscbot resolve checklist not complete again now just waiting for 1 more tick here and confirmation from @richvdh that the backwards compatibility story is sufficient
All the relevant info is in the request log line which includes the request content, but I'd guess it's either a conduit bug or someone holding the bridge wrong
The log is on the debug level, debug logs are basically always required when looking at logs
Unknown errors intentionally exclude the error as it can be absolutely anything. Some other bridges put it in `info` -> `go_error` in case it's needed for metrics/logs/etc, but `message` is...