6
votes

I got this error when I create new client secret in new project.

  1. That’s an error.

Error: restricted_client

Unregistered scope(s) in the request: https://www.googleapis.com/auth/youtube.readonly

Request Details access_type=offline response_type=code client_id=487794563386-mujtj6b5iatnmvdailldn468gg028p8g.apps.googleusercontent.com redirect_uri=http://localhost:61515/authorize/ scope=https://www.googleapis.com/auth/youtube.readonly That’s all we know.

How could I fix that ?

1
Your getting this in the Google developer console? This doesnt look like an error that google would display there. This looks like an error you are getting from authenticating your application. - DaImTo
Yes, It's error when I open link to authenticating my application. I think google have just update, because don't have error yesterday - ValueTeam
Google doesn't have access to update your application. Please edit your question and include your code. - DaImTo
Having the same problem as well and this was working fine yesterday. Luckily just doing some beta testing on an app but can't imagine if this was happening with a live app. C'mon Google, what changed and how do we fix? - kanso
I also get this error now when requesting access to the mail.google.com scope. "403 restricted_client". This is the only place I've seen a reference to restricted_client anywhere. I also didn't change anything in my application. - Baard

1 Answers

0
votes

403 errors are errors with the users access. The user you are currently authenticated with does not have permission to do what you are trying to do in your case it appears to have something to do with the following scope.

https://www.googleapis.com/auth/youtube.readonly

Its hard to know what you are doing without seeing your code. I suggest you attempted to authenticate your user again. IF you changed the secret then its not going to work with a refresh token generated by another secret.

I am going to contact Google to be sure that there hasnt been any changes recently. I cant see anything in the change logs myself. There may have been a stealth change that they didnt release.

Status