Trying to obtain an Access Token for IndiePub with IndieAuth to be used in IFTTT requests so I can link other Web Services with my site.
I was able before to get a token using, and the integration with Pocket, Deezer and others worked, but I revoked all access tokens and today it no longer works to create a new token on my Known instance running version 1.2.2.
This post is about trying to solve this issue.
Got the endpoints of my server using:
After entering all the fields in "Gimme A Token" and going through the process to get the access token, I end up onwith the message "Client mismatch". And I'm not sure where to go next.
What is causing this "client mismatch"? Did Known get safer or is "gimme-a-token" broken?
Going to reach out to Seb and Marcus in the next days.
Found that Greg had a similar issue with Monocle some months ago:
Update 2020-06-29 19:00
So I can rule out that "Gimme-A-Token" is broken.
Thanks to the greate people on the #knownchat IRC channel (thanks Aaron, Greg and sknebel) I have a pointer towards htaccess and http/https redirecting. Looking into that now.
Update 2020-06-29 23:20
It seems that for a correct IndieAuth authentication, I had to add a hard-coded "me" url in the head of the Known head.tpl.php file so the Known homepage would always have this link:
This resolved thesite error message and I can log in in one flow without having to retry.
But unfortunately I'm still getting "Client mismatch" errors with "Gimme a token" most of the time. I did manage to get once an actual token which I can now use again for IFTTT PESOS syndication.