Guys
I get this notice in the debug log, its easy enough to fix so when you do an update maybe add it to the fixes.
register_rest_route was called incorrectly. The REST API route definition for indieauth/1.0/token
is missing the required permission_callback
I have this working in terwsm of logging an existing user with a url on via indieauth. But what about a potential new user?
Does this plugin handle regsitering a new user in any way? i cant seem to find anything like that in the code…
The spec talks about parsing a hcard but I don′t think this is a secure way of creating a new user.
]]>I get this message in the plug-in setting page:
Authorization has Failed
The authorization header was not returned on this test, which means that your server may be stripping the Authorization header. This is needed for IndieAuth to work correctly.
If you are on Apache, try adding this line to your .htaccess file:
SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
If that doesnt work, try this:
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
If that does not work either, you may need to ask your hosting provider to reconfigure to allow the Authorization header to be passed. If they refuse, you can pass it through Apache with an alternate name. The plugin searches for the header in REDIRECT_HTTP_AUTHORIZATION, as some FastCGI implementations store the header in this location.
I’m sure you’ve seen that before. So I contacted Pressable, my managed web host and got this answers.
“Based on our documents, we do pass Authorization headers.
“It will be best to check with the plugin’s developer/support team to shed light on what’s causing the issue. If they can provide more information of what needs to be checked/done from our end, we can check on this further.”
So any help here would be good.
]]>Running WordPress and I see the following error for the IndieAuth plugin: “The authorization header was not returned on this test, which means that your server may be stripping the Authorization header.” I’ve tried both of the recommended solutions but the error persists. I am able to login into Quill and Aperture but Monocle fails with 403 Forbidden. How can I ensure the authorization header is getting returned?
Thanks in advance for any advice on this.
WHen I try to log into indieauth.com I get “There was an SSL error connecting to https://<website>”
When I try to log into Quill, I get “error_fetching_url
There was an error fetching the profile URL when checking for redirects.”
WHat am I missing here to get this working?
]]>Hi!
I’ve tried to implement indielogin on my web site https://alias.erdorin.org and everything seems to work properly, until the very last phase:
Any idea about what is wrong?
Many thanks in advance!
]]>I’ve got the indieauth plugin installed, and it seems to work, but when I try to do something on my site with a remote tool it fails with “unauthorized.”
Looking at the initial response I see:
{ “access_token”: false, “token_type”: “Bearer”, “scope”: “create update media”, “me”: “https://philipbrewer.net/” }
I’m guessing that “false” where the token ought to be is the source of all the problems I see later.
Any debugging suggestions welcome.
]]>Whenever the IndieAuth plugin is enabled I get an error exporting images from Adobe Lightroom to my WordPress blog.
“Some export operations were not performed”.
The Adobe Lightroom plugin is at https://apps.wordpress.com/lightroom/.
I see no relevant error in the apache logs.
]]>I activated IndieAuth and was able to link it to GitHub, but when I try and login to my WordPress admin I get the following message if I leave out the username and password:
Your have entered a valid Domain, but you have no account on this blog.
How do I associate my self hosted WordPress account with what IndieAuth is looking for? The message offers no help link and the plugin doesn’t have any settings.
TA
]]>