Closed jk-na closed 1 year ago
Ah, GoToSocial! Memories of #1340. Sounds like we maybe got a bit further this time, but still not all the way?
Yes, pretty much, been somewhat strapped for time so haven't been able to raise tickets of late. I suspect that we are close and hoping the remaining hurdles are simple enough to overcome!
Looks like the issue is that Mastodon's API for creating OAuth apps lets you pass multiple redirect URLs in redirect_uris
, separated by newlines, https://github.com/doorkeeper-gem/doorkeeper/pull/298, which Bridgy does, and it looks like GtS might not support that.
They're tracking this in https://github.com/superseriousbusiness/gotosocial/issues/962 now. Tentatively closing here, feel free to reopen if we need to do anything on Bridgy's end!
What happened?
Approve the oath request: Application Bridgy (https://brid.gy/) would like to perform actions on your behalf, with scope read:accounts read:blocks read:notifications read:search read:statuses.
The application will redirect to https://brid.gy/mastodon/callback to continue.
What you expected to happen?
To be able to authenticate with brid.gy in order to enable the application to interact with my GtS account
How to reproduce it?
Same steps as above
Anything else we need to know?
The errors from the syslog on the gts server:
The url of the callback: https://brid.gy/mastodon/callback?error=server_error&error_description=The+authorization+server+encountered+an+unexpected+condition+that+prevented+it+from+fulfilling+the+request&state=11
Text on the resulting html page.
Bad Request
_servererror The authorization server encountered an unexpected condition that prevented it from fulfilling the request
I am not sure if the issue lies on the gotosocial side, the brid.gy side or a bit of both so will raise the same issue on both gts & bridgy github pages.
GoToSocial ticket: https://github.com/superseriousbusiness/gotosocial/issues/1327