The error seems to reflect that your credentials are wrong. What is the URL you are hitting? Is that dev or prod?
Can you please check with developer support and submit a help ticket with your application client id so that they can check the issue?
We are using the production clientid and client secret provided by RingCentral.
We are using the following code to create the client.
RestClient rc = new RestClient(RINGCENTRAL_CLIENTID, RINGCENTRAL_CLIENTSECRET, false)
Then the following code to authorize.
TokenInfo tokenInfo = await rc.Authorize(RINGCENTRAL_USERNAME, RINGCENTRAL_EXTENSION, RINGCENTRAL_PASSWORD);
During the auth, exception is thrown.
I see you are using the RingCentral .NET SDK. To authenticate with the production credentials, change the last param to true.
RestClient rcsdk = new RestClient(PROD_CLIENTID, PROD_CLIENTSECRET, true);
Thanks Phong! I did switch to
RestClient rc = new RestClient(RINGCENTRAL_CLIENTID, RINGCENTRAL_CLIENTSECRET, true);
The auth still uses https://platform.devtest.ringcentral.com/restapi/oauth/token to authenticate.
I have sent a request to the developer support team as recommended by @Anirban Sen Chowdhary.
I am still facing auth issues. The request is as follows.
Method: POST, RequestUri: 'https://platform.ringcentral.com/restapi/oauth/token', Version: 1.1, Content: System.Net.Http.FormUrlEncodedContent, Headers: { X-User-Agent: Unknown/0.0.1 RingCentral.Net/2.0.2 Authorization: Basic R1NNVUxRMnhTVGV2RnhaSVFsb0tidzo3WHVwRFY3X1IzeTNPRlBDMWRwRkRBTnFTeWhuOXRTc3lsSnc3RDdtdGJmUQ== Content-Type: application/x-www-form-urlencoded Content-Length: 79 } Content: <content has been disposed by HttpClient: https://github.com/dotnet/corefx/issues/1794>
App has graduated to production. However it is still active in sandbox. It is confusing.
When your app is active in the production, it is also still active in the sandbox environment. So don't worry about that because it means you still can test the app in the sandbox at the same time.
1. Make sure to use the client ID and client secret for different environments accordingly.
2. Make sure you login the app with user's credential under each environment correctly.
Your last update showed the correct URL for the production so I am not sure why you can not get authenticated.
'https://platform.ringcentral.com/restapi/oauth/token'
Is this a free tier app?
The last thing now I can guess is being a free tier app.
As per my conversation with the backend dev support team was when I was facing similar kind of issues not able to test the app in production.
What they said was free tier app will not be able to test it using our account and any other RC user (paid user) can test the integration app in production.
Now I hope this is not the case with you.
We have the same issue: cannot login users with the account details configured for production environment. What is the solution for this issue?
This is normally because of some mistakes in your user credentials, server uri etc. Recommend you to double check them. If you still have problem, create a new thread and provide some some code snippet.
I double checked the credentials and they are correct, I think as we can use it to login the default admin user but no other users. I have started another thread:
https://community.ringcentral.com/questions/90997/user-authorization-failure-with-error-invalid-reso-1.html?childToView=91004#answer-91004
Using the RingCentral Phone for Desktop, you can dial or receive test calls, send and receive test SMS or Fax messages in your sandbox environment.
Download RingCentral Phone for Desktop:
Tip: switch to the "sandbox mode" before logging in the app:
4 People are following this question.