We are performing oauth against a sandbox app. The generated url is https://platform.devtest.ringcentral.com/restapi/oauth/authorize......................... Which is normal. As of just recently, that is now 302'ing us to `https://login.ringcentral.biz ` Which is complaining about sandbox accounts not being supported. Is there a path forward? This is new. It was working just a couple days ago and we were not being 302'd
,I tried to perform oauth against a sandbox app. The url generated was `https://platform.devtest.ringcentral.com/restapi/oauth/authorize ...............` as usual but that URL is now 302'ing me to `https://login.ringcentral.biz `. And logging in there tells me that sandbox accounts aren't supported.
The 302 is new. It never did that before for us. Is there a path forward?
Hi, we are encountering the same issue as @Ben Ashby . We have been using "https://platform.devtest.ringcentral.com/restapi/oauth/authorize" for testing for a long time, and it's been working okay until recently. Now it always redirects us to "https://login.ringcentral.biz."
Are there any changes happening or is it currently under maintenance?
In addition, when logged into the developer portal, Sandbox Environment Online Account Portal Link here
Is landing us here
Can you clear your browser cookies and retry? And hold on on the OAuth, it seems there is a temporary issue and I asked the team to investigate it.
Are you on a mobile device, tablet or iPad etc.?
I am not sure about why it took you to ringcentral.biz.
What are other parameters you used with that endpoint? Your app authentication is 3-legged OAuth, right?
When it is time to perform oauth we generate the following URL (formatted for convienence)
https://platform.devtest.ringcentral.com/restapi/oauth/authorize?
&redirect_uri=https://our-endpoint-to-receive-the-code
&client_id=Sgg-6WhrRSiHkNBeljhE6g
&state=STRING_WE_LOCALLY_USE_TO_IDENTIFY_CLIENT
&code_challenge=FhqvHz1NzG5NLGSdA06mcjUm2hwNTeOC-4NuOMkDkRM
That has always just let us login straight to https://platform.devtest.ringcentral.com. But is now returning a 302 with the Location header
Does that provide you with the information you needed? I am not 100% sure about the 3 legged oauth. We have been doing this for quite some time successfully and haven't changed anything on our end.
A new Community is coming to RingCentral!
Posts are currently read-only as we transition into our new platform.We thank you for your patience
during this downtime.
Try Workflow Builder
Did you know you can easily automate tasks like responding to SMS, team messages, and more? Plus it's included with RingCentral Video and RingEX plans!Try RingCentral Workflow Builder
