Setting file backend to the default for RStudio Server [Pro] #95
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request sets the
file
backend by default on Linux servers where the secret service is not running.On RStudio Server and RStudio Server Pro, keyring defaults to the
env
backend today by default, because the secret service is designed to run on desktops, not servers (see #53, #72, and #77). However, thefile
backend provides a superior experience to theenv
backend on the server. Users can store encrypted secrets to disk with thefile
backend, whereas theenv
backend only holds passwords for the life of the R session. Thefile
backend throws no warnings, whereas theenv
backend throws warnings.