Skip to main content
Question

My public app in prodcution suddenly getting 400 bad requests paid users from other accounts are not authorising

  • October 29, 2021
  • 5 replies
  • 685 views

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




5 replies

  • New Participant
  • 1 reply
  • November 2, 2021

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.
1635835521936.png


PhongVu
Community Manager
Forum|alt.badge.img
  • Community Manager
  • 2317 replies
  • November 2, 2021

What is the ticket number?


PhongVu
Community Manager
Forum|alt.badge.img
  • Community Manager
  • 2317 replies
  • November 2, 2021

Is this affected a certain user or all users?


  • 0 replies
  • November 2, 2021

BrightGaugeSoftware : Asking the support team to take a look into the ticket : 13889695

@Mohan , Have you opened Dev Support ticket ?



PhongVu
Community Manager
Forum|alt.badge.img
  • Community Manager
  • 2317 replies
  • November 3, 2021

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.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings