Add `install` and `overwrite` parameter to `set_auth_token()` to allow token to persist across sessions about arcgisutils HOT 3 OPEN

The important thing to note here is that we are not using API keys but rather using access tokens which by design have an expiry unlike API keys. The only type of access token that can be refreshed non-interactively is the auth_code() result—which is actually a really good thing to document for non-interactive workflows....

I know that httr2 allows for caching which I tried understanding once but despite a real attempt, failed (r-lib/httr2#210). I think this should be explored before writing bespoke code that writes very sensitive information to disk.

Additionally, I think it should be a follow up to R-ArcGIS/arcgislayers#128

from arcgisutils.

I know we talked about it in R-ArcGIS/arcgislayers#3, but think it makes sense to revisit adding keyring as an optional dependency and allowing that to be the mechanism for storing credentials. It will support the secure backend provided by the operating system, and allow the OS based password management interfaces to be used independently of R when useful and help minimize the chances of credential leaks from the environment table.

from arcgisutils.

@elipousson, have you been able to retry the auth_user() function? There was an issue with one of the request parametes. set_arc_token(auth_user()) is non-interactive and will let us read and write private content.

from arcgisutils.