Authenticate oracle data base from r script

[jcblum]

There’s been a fair bit of discussion on similar topics before — you might look st these threads for some more ideas:

What is your solution for credentials access on RStudio Server?

I love the keyring package, however it's been suggested that it currently doesn't play well with RStudio Server. Community hive mind, what do you use to store/access things like database credentials outside of your mainline code? I've come across the config package. Are there any alternatives? Or is there plan for keyring support soon?

Secure way to store database password in package with front-end API to database

I am working on an internal package that will act as a front end to different databases and return data in a structured tidy format. The databases are all accessed via DSN but still require the username and password for odbc::dbConnect() to work. The usernames have read-only privileges on the databases The package will be hosted on a private CRAN mirror behind my corporations firewall. My question is what is the best way to store the credentials of the database in a secure way in the package. To make things more interesting, this will also likely be used on a Connect server, which may make a few of the options given here a little more difficult. I have read through the linked article seve…

Storing user database connection information for package use

I'm creating an R package where the user will first have to connect to a database using the DBI and odbc packages. Subsequent functions will then need to query the database database and then conduct some sort of analysis. So the workflow for the user is (1) connect to the database; (2) do something that depends on the connection. e.g. connect_to_db() analyze_using_db_connection() I'm not sure of the best setup to make things easy on the user and myself, the developer. As I see it, here are my options: (1) for every function in the package have a con argument where the user passes the connection (this seems less than ideal for anyone using the package) (2) Use some sort of class system l…

Keeping API Keys Private in Blogdown

I'm in the process of writing a blog post that queries an API without an associated R package. Because there's no associated R package, I'm using the httr GET function which requires my API key to be in the string format. My question is, how do I keep my API key private so it doesn't show up in my website's public GitHub repository? I'm familiar with caching API keys using options( ) as in options(tigris_use_cache = TRUE) for the tidycensus package but not sure how/whether to implement this in rmarkdown/blogdown for the API I linked to above. I haven't been able to find much help from Googling so any insight/tips would be greatly appreciated.