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

OAuth vs Keys #97

Open
joshtorres opened this issue Apr 15, 2021 · 2 comments
Open

OAuth vs Keys #97

joshtorres opened this issue Apr 15, 2021 · 2 comments

Comments

@joshtorres
Copy link
Member

@drewroberts I see we have Keys to add the API keys, but I believe this requires each company to add their API keys for each product. I just want to confirm this is still the direction you want to go and not have OAuth to pull in the keys automatically for each account.
@phuclh

@drewroberts
Copy link
Member

When I set it up in the application, I added all of the products to the same Key. I don't think that web endpoint was moved yet to that package. Can you check?

I prefer using Keys so that we can have some Laravel apps that have multiple accounts in there.

@phuclh
Copy link
Contributor

phuclh commented Apr 15, 2021

@drewroberts I am adding Google Search Console API to the SEO package. So If we using Keys, the customer has to go to the Google Platform Console Dashboard to copy the key and then go to TGER Key resource and create the key while using OAuth, the access token is saved in a JSON file, the customer don' need to go over above steps. Moreover, we still have multiple accounts by creating multiple JSON files.

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

3 participants