The API key and "secret" aren't actually secrets so you can include in the package.
Hadley On Friday, June 5, 2015, Neal Fultz <nfu...@gmail.com> wrote: > I am working on updating the RGoogleDocs package to use OAuth2, since the > old api was recently turned off (at my job we use it as a poor mans > database). > > As part of the auth process, I need to send google a client key and secret > in order to gain access to a spreadsheet. Is there a 'safe' place to store > the secret? > I would strongly prefer not requiring my end users to have to sign up for > their own google API keys, but I also do not want to store the secret in > the clear. > > Any suggestions on best practices? > > -Neal Fultz > > [[alternative HTML version deleted]] > > ______________________________________________ > R-package-devel@r-project.org <javascript:;> mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel > -- http://had.co.nz/ [[alternative HTML version deleted]] ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
