Mastodon login and interactive publish broken due to Mastodon/doorkeeper OAuth bug

[troutcolor]

Hi,
I had this working on my blog posting to mastodon.social using the Syndication Links plugin and then it stopped working.
I not sure if the bridgy log will help or not.

Trying on the bridgy site, I get to this mastodon page not sure if that will work? This says "We're sorry, but something went wrong on our end."

Hopefully that makes some sort of sense?
Cheers

john

[snarfed]

hey, sorry for the trouble! could you try disabling and re-enabling publishing on https://brid.gy/mastodon/@johnjohnston@mastodon.social and see if it works then? i've seen this scope issue with mastodon before, but i'm still trying to track it down.

[troutcolor]

Hi, thanks. I just tried that and resubmitted a post through the bridgy page. I got the same result.
Is there any other information I can send that might help?

Cheers
John

[snarfed]

thanks for trying! that's all i need, i'll investigate.

[snarfed]

oh god, also, i just noticed the mastodon page link you originally posted included bridgy's client secret for mastodon.social. 😐 i'll reset that. please be careful when posting URLs from login and auth flows! (basically, don't unless you know what you're doing. 😁)

[troutcolor]

oh god, also, i just noticed the mastodon page link you originally posted included bridgy's client secret for mastodon.social. 😐 i'll reset that. please be careful when posting URLs from login and auth flows! (basically, don't unless you know what you're doing. 😁)

I certainly don’t know what I am doing. Thanks!

[snarfed]

i reproduced this tonight and suspect something wrong on mastodon's end: mastodon/mastodon#12915 . let's see what they say.

[joebuhlig]

I might have a related issue. I continue to get the yellow pause icon. I can revoke access on Mastodon, log out of Bridgy, and then reinstate everything. But the issue returns. It seems like it's an authorization issue on Mastodon's side, but I can't find any errors to share.

[snarfed]

oops, sorry @joebuhlig! my fault, looks like an unrelated bug. thanks for the nudge! i think i've fixed it now, mind trying again?

[joebuhlig]

Just tried the yellow pause button again. It asked for an authorization and then after a couple minutes returned with the pause button again. Do I need to revoke, log out, and start over?

[snarfed]

no, sorry, my fix needed a bit more to it. deployed that now and tested locally. mind trying again? thanks for your patience!

[joebuhlig]

Bingo! Thank you much!

[hs0ucy]

I have the same problem. I tried with the form, then with cURL.

`curl -d 'source=https://hugo.soucy.cc/note/2020/02/lost-connection-to-the-earth.html&target=https://brid.gy/publish/mastodon' \

https://brid.gy/publish/webmention
{
"error":"Couldn't find link to brid.gy/publish/mastodon"`

I disconnected and reconnected but the result is the same.

My mastodon instance is not mastodon.social but mastodon.sdf.org.

Thanks

[hs0ucy]

I have the same problem. I tried with the form, then with cURL.

`curl -d 'source=https://hugo.soucy.cc/note/2020/02/lost-connection-to-the-earth.html&target=https://brid.gy/publish/mastodon' \

https://brid.gy/publish/webmention
{
"error":"Couldn't find link to brid.gy/publish/mastodon"`

I disconnected and reconnected but the result is the same.

My mastodon instance is not mastodon.social but mastodon.sdf.org.

Thanks

[snarfed]

@hs0ucy that looks like a different problem. as the error message says, your post needs to link to https://brid.gy/publish/mastodon . see https://brid.gy/about#webmentions

[hs0ucy]

@hs0ucy that looks like a different problem. as the error message says, your post needs to link to https://brid.gy/publish/mastodon . see https://brid.gy/about#webmentions

Oh, you're right ... In my template i had https://fed.brid.gy 👎 :/

Thanks!

[jee-r]

@GitHub

Hello, Is there a cli way to verify if bridgy is connected to mastodon instance and if is not the case to reconnect it ?

I was thinking something like authorize it with an app https://mastodon.social/settings/applications/new

It’s can be a workaround to avoid unintended disconnection

Thank’s

#bridgy #disconnection #mastodon #cli

(Originally published at: https://jeer.fr/micro/1582197847)

[snarfed]

@jee-r hmm! are you seeing your bridgy mastodon account get repeatedly disconnected? is that related to the interactive publishing problem here?

[jee-r]

@snarfed i don't know if it's a real disconnection but sometime when i try to publish i get the error message out of scope when it's happened i need to disconnect from bridgy, remove the bridgy's app authorization in mastodon's settings and reconnect again. You are right it's may be more related to #894 than this issue, if it's happened again i'll report rather there.

[isellsoap]

I have the same error since a few weeks now (see a recent log with the authorization error).

The set up on my side should be correct (I think). When trying to send a webmention to Mastodon via Bridgy, the Mastodon Bridgy page shows the pause button ("This account was disconnected on Mastodon's end. Click to reconnect it!"). If I repeat the process after reconnecting the account, the same pattern occurs.

[snarfed]

I looked at this a bit again recently. Looks like the Mastodon bug is a URL length limit that the OAuth redirect URL hits on their end. It's a bit inconsistent, but definitely there, across instances. Details in mastodon/mastodon#12915 😐

[snarfed]

Discussion is now in doorkeeper-gem/doorkeeper#1554, tentative conclusion is that the issue is in doorkeeper. Still not much more movement though. 😐

[snarfed]

I'm going to try to work around this by shortening the redirect URL on Bridgy's side. indieweb.social and mastodon.art aren't reproducing it right now, but mas.to is.

[snarfed]

It worked! Specifically snarfed/oauth-dropins@1e987be, snarfed/oauth-dropins@0ba0f71. I think we're back in business with Mastodon login and interactive publish.