Conversation
supportI have tried to create a new post with both https://micropublish.net/new and https://quill.p3k.io/new but they seem to fail. Both services could authenticate just fine. Quill says: Your endpoint did not return a Location header. See Creating a Micropub Endpoint for more information. ` HTTP/1.1 403 Forbidden Date: Mon, 30 Jul 2018 06:53:34 GMT Server: Apache Expires: Wed, 11 Jan 1984 05:00:00 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Link: < https://test-wp.robertvanbregt.nl/wp-json/indieauth/1.0/token> ;; rel=”token_endpoint”, < https://test-wp.robertvanbregt.nl/wp/?micropub=endpoint> ;; rel=”micropub”, < https://test-wp.robertvanbregt.nl/wp-json/webmention/1.0/endpoint> ;; rel=”webmention”, < https://test-wp.robertvanbregt.nl/wp-json/webmention/1.0/endpoint> ;; rel=” http://webmention.org/” ; Strict-Transport-Security: max-age=300; includeSubdomains; Vary: User-Agent Upgrade: h2c Connection: Upgrade Transfer-Encoding: chunked Content-Type: application/json {“error”:”insufficient_scope”,”error_description”:”scope insufficient to create posts”} `
Some additional info. With https://micropublish.net/new I first logged in with full access. That failed. When I login with “post” access only, I succeeded. The authorization returned does not use spaces (” “) as separator, but the encoded “%20” instead. Perhaps this is creating the problem?
ugh. sorry for the trouble! hey @dshanske , any ideas? more importantly, would you mind writing up a blog post with the common causes and solutions you’ve seen so far?
I tried to re-authorize with https://quill.p3k.io/new and use the ‘create’ scope instead of ‘create update’ I did earlier. The ‘create’ scope worked as well, so I’m almost certain is has to do with the double scopes and spaces.
This is an IndieAuth bug introduced in the last update, not a Micropub bug. I’m going to see about pushing the fix. The PR was merged a few days ago.
I have updated the IndieAuth plugin and re-authenticated with Quill and create+update is now working. Thanks.
Some additional info. With https://micropublish.net/new I first logged in with full access. That failed. When I login with “post” access only, I succeeded. The authorization returned does not use spaces (” “) as separator, but the encoded “%20” instead. Perhaps this is creating the problem?
ugh. sorry for the trouble! hey @dshanske , any ideas? more importantly, would you mind writing up a blog post with the common causes and solutions you’ve seen so far?
I tried to re-authorize with https://quill.p3k.io/new and use the ‘create’ scope instead of ‘create update’ I did earlier. The ‘create’ scope worked as well, so I’m almost certain is has to do with the double scopes and spaces.
This is an IndieAuth bug introduced in the last update, not a Micropub bug. I’m going to see about pushing the fix. The PR was merged a few days ago.
I have updated the IndieAuth plugin and re-authenticated with Quill and create+update is now working. Thanks.