Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

403:Access denied error on last step of personal API walkthrough #312

Closed
ferfey opened this issue Jun 5, 2022 · 6 comments
Closed

403:Access denied error on last step of personal API walkthrough #312

ferfey opened this issue Jun 5, 2022 · 6 comments

Comments

@ferfey
Copy link

ferfey commented Jun 5, 2022

I followed the walk through and on the second device ID screen I received the following error
ECB86475-7E37-47AC-837D-05670CB7AEBC

I tried to use the “less secure apps” option but that feature has been disabled by google.
Is there some other setting in Oauth or credentials that needs to be tweaked to give my Kodi add on access?

@Duke999R
Copy link

Duke999R commented Jun 7, 2022

G'day,

I was getting this error on the second code as well. I went back into the oauth consent section and clicked "publish". https://i.imgur.com/KBudxAO.png Then the second code worked and I signed in... should work for you.
Screenshot_94
.

@Niquarl
Copy link

Niquarl commented Aug 10, 2022

Thank you, the fix worked for me too. Perhaps one should consider updating it on the wiki.

@volkanpaksoy
Copy link

This worked for me too.

Is there a security risk involved? Google warns that "Your app will be available to any user with a Google Account". Does it pose a risk without them having the API key and OAuth credentials?

@Duke999R
Copy link

I'm pretty sure that it only causes an issue if someone else gets access to the keys and such. Keep them safe and you should be fine. I've had no issues so far.

@SpeckiJ
Copy link
Contributor

SpeckiJ commented Oct 27, 2022

As an alternative to publishing you can add your Account as a Test User, thereby allowing access. By default nobody (not even the account owning the project) has access.

oauth

@KnightOfCups
Copy link

For what it worth, I'd like to emphasise that before facing the issue I had to complete the sign-in process under the private mode of the browser. For unknown reason, it failed in normal mode with this cryptic message "Sorry, something went wrong there. Try again."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants