Closed chipoglesby closed 6 years ago
Yes, at the moment the native client Id/secret options are run when you use scr_auth()
- if you want to avoid that you could use googleAuthR::gar_auth()
for more customisation.
Since the webmasters API is a lot more generous we've never seen the need to require people to use their own client Id, and I think the assumption is if you require that then you are ok with the more technical but customised solution using googleAuthR::gar_auth()
directly, but let me know if this is off :)
If interested, the API limits are 100 million a day, 2000 calls per 100 seconds per user, which we're way under globally.
Okay. It sounds like scr_auth()
might work. I just have to reauthenticate each day when I run my script. I'm trying to automate this process, but it's not working because I always have to open my browser and get a new token.
If you specify the filename, it should refresh itself:
scr_auth("my_token.oauth")
Thanks @MarkEdmondson1234, I'll try that.
I was reading through the documentation and I'm curious if the settings in
inst/clients/native.json
are overwriting when you setoptions()
aR
file like:Here's an example of my code, but when I go to authenticate, I'm taken to the Google Cloud Console settings that are listed in
inst/clients/native.json
instead of what I've used in options.