Hello Team,
Our app public app (live in Production) and is working fine for long time but suddenly we are getting below mentioned response and we are using RingCentral SDK, 3-legged authorization flow
{
"error": "invalid_client",
"errors": [
{
"errorCode": "OAU-123",
"message": "Client authentication is required"
}
],
"error_description": "Client authentication is required"
}
and our client id is: MPI3D5LuTHqVlzzUJcwvtA
Thanks in advance
Is this affected a certain user or all users?
After checking with the engineers. I learn that recently we reenforce OAuth with the client id and client secret in the auth header. So if your current auth code does not include the client secret, it will fail with the error codeOAU-123 as you reported.
https://developers.ringcentral.com/api-reference/Authorization
For confidential clients (server applications) client_id
is not enough, you need to provide Authorization
header (containing Base64-encoded client_id
and client_secret
) or client_assertion
parameter via JWT client request.
Please update your oauth header and try again.
Let me know if this helps.
Also I am getting same error with 3-legged authorization flow(Server side web app) settings. created ticket as well but no response from them.
What is the ticket number?
Case number - 13889695.
It got closed without resolution.
[ { "errorCode" : "OAU-123", "message" : "Client authentication is required" } ], "error_description" : "Client authentication is required" }.
This is the error we are getting.
Let me check with the support team. Meanwhile, can you share the app client id? And let me know if this impacts all users or just a certain user?
Thanks @Phong Vu
Client id(Production) - dA4ZFiACRYqFrwh7yf4TMg
Client id(Sandbox) - EfRwWhJeQQWDQNC_xJya_g
In both environment we are getting this.
Yes it's impacting all the users whenever they try to Authorize in our application.
We are getting this error after user gives consent and then while calling token API.
How do you implement the OAuth? Do you use a RingCentral SDK? I just test using your app credentials and run my own code to login and I was successfully login the app with 2 different production accounts.
Note: I was using your local redirect uri "/api/ringcentral/redirect/"
We are using request_oauthlib Python lib for our all Oauth2 Intigrations.
If you are able to hit token API and why are we getting issues?
We are getting issues in local as well as production. So it's impacting our all business partners.
Please let us know what we can do for this.
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