redirect_uri_mismatch

Hi  -

I believe you have also raised a case with our support team on this question. I'll post here what will also be shared via your active case. An error stating "redirect_uri_mismatch" indicates that there is a mismatch between what you have configured in your application for the 'redirect_uri' and what you are passing through the first leg of the OAuth process. To validate what you have set as your Redirct URI...

1. Go to developers.box.com
2. Login to your developer account
3. "Edit Application" for the Content API application you're using
4. Scroll down to the section that allows you to input a "redirect_uri" under "OAuth2 Parameters".

Make sure that what you have listed in this field matches exactly with the parameter you are sending in your request to the OAuth endpoint.

I am encountering this same issue when attempting to connect with an IBM Box adapter in their Security Identity Manager. I reviewed the directions above but their doesn't seem to be any available OAuth2 settings in the current setup. Is there still a way to see what the redirect_uri_mismatch conflict is? I am using the exact hostname that is connecting and the adapter is properly redirecting to it's token generation app. 

I have this same problem, but there's no longer an option to input the "redirect_uri" under the OAuth parameters. So how do I fix it without that option?

I have the same problem and I don't see an option to input the "redirect_uri". Is there an option to fix this issue?

I have the same problem, and have filed a support case. This is an urgent issue for us and I need an option to fix the issue asap. 

Hi, has anyone found a solution to this?

1519221647001 The solution that worked for us was using the JWT auth method. Our script is written in python(3.9), and is utilizing the Box SDK to read and write to the platform. We were running on AWS/Azure with functions and lambdas (respectively), and they were failing to authorize. Once we switched to the JWT auth method, everything else functioned as expected even with the remote/temp servers running the code.