authentication failing on login
maddler opened this issue · comments
Hello,
I've just installed Toot's latest version and trying to login via "toot login" but it fails with "Client authentication failed due to unknown client, no client authentication included, or unsupported authentication method" error.
❯ toot env
toot 0.38.1
Python 3.11.6 (main, Oct 2 2023, 13:45:54) [Clang 15.0.0 (clang-1500.0.40.1)]
macOS-14.1-x86_64-i386-64bit
Steps to reproduce
- launch "toot login" on the command line
- provide instance
- provide login details
- open provided link in browser
Current outcome: error "Client authentication failed due to unknown client, no client authentication included, or unsupported authentication method."
Expected outcome: authentication completed.
I confirm this bug report. My env:
toot 0.38.1
Python 3.11.5 (main, Sep 2 2023, 14:16:33) [GCC 13.2.1 20230801]
Linux-6.5.9-arch2-1-x86_64-with-glibc2.38
I cannot reproduce this, and I'm not sure I understand the issue.
Steps to reproduce
1. launch "toot login" on the command line 2. provide instance 3. provide login details 4. open provided link in browser
So does your server show you this error in the browser? If it's not a secret, what server are you trying to log into?
Yes, the error is being shown in the browser.
Server is https://mastodon.ie.
if that's of any help, same process works flawlessly with other CLI clients (tut).
Thanks!
Same for me, server: floss.social
I registered on floss.social to try to reproduce this, but did not have any issues. Server gave me the code after logging in. 🤔
uhm, I've got 2FA enabled. That or anything else in the account preferences?
But with tut it works fine and the generated URL looks pretty much the same.
So, I removed an existing config.json file (was trying to login again as I was getting some session errors, if I recall correctly, before) and that's working now.
It's something with the client registration. Could you please edit your ~/.config/toot/config.json and remove the entry for floss.social? The part outlined in red here:
And then try to log in again, it will create another client id.
So, I removed an existing config.json file
Yeah, that would work too.
Thanks for your help!