I’m trying to implement OAuth2 “account linking” in my project so people who contribute translations can manage how their name appears on the website of the project. This is a not-for-profit public open-source project, and as such my Crowdin account also does not have any kind of active subscriptions.
I created the authorization link based on the docs, however opening it leads to a “403 Unauthorized” default error page.
Can you please help shed some light on why this might be happening?
Hi @DJDavid98 ,
Could you please share the steps you took to create the link? Perhaps you could make the screenrecording and send it to support@crowdin.com? Would you please also send me the link to any of your projects?
OAuth 2 applications do not belong to any project, I’ve simply created an application in my account and I’m trying to authorize it, the client id is in the URL which should be enough for you to see that the application exists in my account. I created to following your own API documentation regarding how to construct OAuth authorization urls found at: support[.]crowdin[.]com/developer/authorizing-oauth-apps/
This authorization page is throwing a blanket 403 for no discernible reason, with, as far as I can tell, the correct parameters.
I figured out the issue, your moderation team got rid of the authorization URL in the original post, but I was using a local development redirect_uri parameter that had 127.0.0.1:8000 as the host, which evidently this service does not like. I changed it to localhost:8000 and the flow started working.
Hi @DJDavid98 ,
Thanks a lot for the update! Glad to hear you figured it out — indeed, Crowdin OAuth doesn’t accept 127.0.0.1 as a valid redirect_uri, so switching to localhost was the right call 