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

Please pull Wiki update for Google API-key #934

Open
Kuschranada opened this issue Oct 13, 2024 · 5 comments
Open

Please pull Wiki update for Google API-key #934

Kuschranada opened this issue Oct 13, 2024 · 5 comments
Labels
enhancement New feature or request

Comments

@Kuschranada
Copy link

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.


@Kuschranada Kuschranada added the enhancement New feature or request label Oct 13, 2024
@MoojMidge
Copy link
Collaborator

Thanks for the contribution

  1. 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?

@Kuschranada
Copy link
Author

Kuschranada commented Oct 20, 2024

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

  • which Api is to activate
  • where you can create the necessary values
  • set the consent screen to "PUBLISH APP"

@MoojMidge
Copy link
Collaborator

  • 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.

@dekimsey
Copy link

I ran into this trying to understand what the correct values for the API Key, API I'd, and API Secret are supposed to be. However, I wanted to point out the suggested wiki page only refers to API key and OAuth Client ID. It is ambiguous which is which and why it only documents two of the three fields.

Even following the linked guide I still don't know what these values should be.

@MoojMidge
Copy link
Collaborator

There are some visual aids in the pinned issue: #439 (comment)

Have a look at step 12 for clarification on where to retrieve the required values.

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

No branches or pull requests

3 participants