Remi Rampin
Remi Rampin
Again, this is ONLY waiting for maintainers. Stop sending your bots at our issues and patches if you are inactive. This is just rude.
Again, this is ONLY waiting for maintainers. Stop sending your bots at our issues and patches if you are inactive. This is just rude.
To be honest I think the behavior is wrong, but this can probably be patched in the docs if we are not changing behavior.
I think the fact that your own example got this wrong is a sign that the behavior expected by everybody is not what is implemented. I prepared a pull request...
Same remark. Also it does NOT REQUIRE AUTHENTICATION, which is a huge problem. People will base their code off of this and run in the most insecure way. edit: opened...
This also fixes other issues with the example, such as the username not being decoded from bytes (so no row would ever be found in the database), Argon2 being used...
I am not sure what you mean by "ahead of time"? When Synapse gets the username and password to check auth, it should allow login if that user has a...
That is why Nextcloud has this `?direct=1` trick to show the username+password form, even though it is disabled. This trick can be implemented in clients. I just need Synapse to...
What about PRs to fix the behavior?
There is actually a hidden option, something you can type in your browser's JavaScript console to log in with a token. I used it a few months back, I don't...