New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
401 http code with invalid access token response: IndieAuth incompatibility #4
Comments
Do you maybe also have another plugin that implements OAuth2, such as IndieAuth? I know the latter returns an error message if the token doesn't match for it, not giving other plugins the chance to authenticate them. |
I submitted a PR at indieweb/wordpress-indieauth#245 |
Yes, I do. Disabling fixed the issue. I see you put in a PR in that repo. |
The PR was accepted but no new version of IndieAuth has been released. To help others who run into this, I'll keep this issue open until they do so. |
Although authentication with my WordPress instance appears to be successful, when I try to post using Elk or Pinafore (and I think Tusky, though it's harder to see the codes and responses), I'm getting a number of 401 responses with "Invalid Access Token."
Previously I was also receiving a number of CORS errors but I believe those are resolved. Notably, the 'instance' and 'authentication' endpoints are returning this response. There are others like 'filters' and 'custom_emojis', but I know those are not yet implemented.
The token is listen on the Mastodon Apps page and ActivityPub and Friends are installed.
The text was updated successfully, but these errors were encountered: