drive_auth_configure {googledrive} | R Documentation |
These functions give more control over and visibility into the auth
configuration than drive_auth()
does. drive_auth_configure()
lets the user specify their own:
OAuth client, which is used when obtaining a user token.
API key. If googledrive is de-authorized via drive_deauth()
, all
requests are sent with an API key in lieu of a token.
See the vignette("get-api-credentials", package = "gargle")
for more.
If the user does not configure these settings, internal defaults
are used.
drive_oauth_client()
and drive_api_key()
retrieve the
currently configured OAuth client and API key, respectively.
drive_auth_configure(client, path, api_key, app = deprecated()) drive_api_key() drive_oauth_client()
client |
A Google OAuth client, presumably constructed via
|
path |
JSON downloaded from Google Cloud Console, containing a client id and
secret, in one of the forms supported for the |
api_key |
API key. |
app |
drive_auth_configure()
: An object of R6 class
gargle::AuthState, invisibly.
drive_oauth_client()
: the current user-configured OAuth client.
drive_api_key()
: the current user-configured API key.
Other auth functions:
drive_auth()
,
drive_deauth()
# see and store the current user-configured OAuth client (probaby `NULL`) (original_client <- drive_oauth_client()) # see and store the current user-configured API key (probaby `NULL`) (original_api_key <- drive_api_key()) # the preferred way to configure your own client is via a JSON file # downloaded from Google Developers Console # this example JSON is indicative, but fake path_to_json <- system.file( "extdata", "data", "client_secret_123.googleusercontent.com.json", package = "googledrive" ) drive_auth_configure(path = path_to_json) # this is also obviously a fake API key drive_auth_configure(api_key = "the_key_I_got_for_a_google_API") # confirm the changes drive_oauth_client() drive_api_key() # restore original auth config drive_auth_configure(client = original_client, api_key = original_api_key)