Closed jk-na closed 1 year ago
As per https://github.com/snarfed/bridgy/issues/1385#issuecomment-1378224069 - brid.gy author Ryan suggests that:
"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, but it looks like GtS might not support that."
Thanks for investigating jon! this is a duplicate issue of https://github.com/superseriousbusiness/gotosocial/issues/962 so I'm gonna close it, but now it's linked in the other issue for the extra info it provides :)
Describe the bug with a clear and concise description of what the bug is.
Trying to authenticate via brid.gy's mastodon oath path and receiving an error after approving the oath request at the GtS side.
What's your GoToSocial Version?
v0.6.0 git-f9e5ec9
GoToSocial Arch
arm64 binary
Browser version
No response
What happened?
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.
brid.gy ticket: https://github.com/snarfed/bridgy/issues/1385