This function does very little when called directly with a token:
If input has class
request, i.e. it is a token that has been prepared
auth_token component is extracted. For
example, such input could be produced by
Checks that the input appears to be a Google OAuth token, based on
Refreshes the token, if it's refreshable.
Returns its input.
There is no point providing
scopes. They are ignored because the
associated with the token have already been baked in to the token itself and
gargle does not support incremental authorization. The main point of
credentials_byo_oauth2() is to allow
token_fetch() (and packages that
wrap it) to accommodate a "bring your own token" workflow.
This also makes it possible to obtain a token with one package and then register it for use with another package. For example, the default scope requested by googledrive is also sufficient for operations available in googlesheets4. You could use a shared token like so:
library(googledrive) library(googlesheets4) drive_auth(email = "email@example.com") gs4_auth(token = drive_token()) # work with both packages freely now
credentials_byo_oauth2(scopes = NULL, token, ...)
A character vector of scopes to request. Pick from those listed at https://developers.google.com/identity/protocols/oauth2/scopes.
For certain token flows, the
A token with class Token2.0 or an object of
Additional arguments passed to all credential functions.
Other credential functions:
## Not run: # assume `my_token` is a Token2.0 object returned by a function such as # httr::oauth2.0_token() or gargle::gargle2.0_token() credentials_byo_oauth2(token = my_token) ## End(Not run)
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.