Open Kuschranada opened 3 weeks ago
Thanks for the contribution
- Setup a "OAuth consent screen"
- It could be possible that this is autmatically done during the cration of the OAuth Client ID,
- if not ...In the left menue click at "OAuth consent screen" and create a new one.
- Fill out the form, all fields with an * are mandatory. In general you can add dummy values.
- It is important to activete this consent screen. For this click at the "PUBLISH APP" button and confirm the dialog window.
I must admit that I have never done this, instead just added any account I use as a test user to the unpublished application.
Do you recall what the consent screen activate dialog says?
Honestly I did it in a little bit other order. When I created the OAuth-Client-ID it automatlicly added the formular of the consent-screen to the OAuth-Client-ID dialog. If you have a consent-screen then google not aks for it and it is not possible to open the creation-formular for the consent screen again. Thats the reason why I have here a lack of information, as well.
But honestly it was not a big deal the important information are
- set the consent screen to "PUBLISH APP"
There is some indication that this may subject the project to automated auditing, which is why I have never done it. Just conjecture, but it may be the reason why sometimes people have their API keys revoked.
What Problem Does This Solve?
If somebody read the current version of the wiki, it is not clear how to setup a the necessary values for api_key, client_id and client_secret. Additonllay it exist no setup for Enable personal API keys in the current version, which can be enabled or disabled.
Suggest a Solution (optional)
Please pull the changes of the fork in Github Kuschranada/plugin.video.youtube/wiki/Personal-API-Keys to make this more clear.