Implicit grant OAuth results in "Invalid redirect_uri" error

[darranmorris]

I am integrating Bitbucket with Netlify and Netlify CMS, which uses client side implicit grant to log in and make changes in the repo. 

I have set up an OAuth consumer on Bitbucket and have added the Netlify callback URL [ https://api.netlify.com/auth/done ]and the necessary write access to Account and Repositories.

I then added the resulting Bitbucket OAuth key and secret to Netlify settings. I also did the CMS setup.

However, when I then try to log in to the CMS through Bitbucket, I get the error message: 

Invalid redirect_uri
This integration is misconfigured. Contact the vendor for assistance.

I saw that on June 5, there was a problem which resulted in this error, but it seems to have been resolved. 

[Shawn Erquhart]

Hey all, Netlify CMS maintainer here - can anyone confirm whether this is only happening on localhost?

[Chan Wan]

Hi, for me it happen to both localhost and also netlify.com deployed URL. 

[Susan Sanderson]

Still happening in Sep 2020 on nellfy.com deployed url. 

[William]

I'm having the same problem. It keeps redirecting to localhost. 

[olaf Siebert]

yes, me too

[olaf Siebert]

Well only option it seems to switch to GitHub 

[adamrobinson]

Im also experiencing this "Invalid redirect_uri" issue when setting up OAuth.

[dgadwa]

I'm experiencing the same error. 

This is my first project using Netlify CMS and Gridsome so it could well be an error on my part. I've started to check my work and came across your post in the research phase.

[darranmorris]

Update: It appears that instead of the Netlify api callback that I entered in the consumer, the redirect_uri parameter in the URL is pointing to my site. 

When I edit the URL parameters manually in the browser to point to the correct callback, things start to work properly.

Any help much appreciated!

[DaveBourne]

Hi Darran

Did you ever figure this out? We have exactly same issue, need to somehow set the Callback URL!

Thanks

Dave

[marc_poggi]

Hi Darran , I am experiencing the same error , 

have you found a workaround in the configuration to make it work  ?

Thanks 

marc