Non-interactive unlocking of file backend keyring?

[mattmoo]

Thank you for this great package!

I tend to use the targets package for architecture, and I am running into a problem with keyring and RStudio Server.

It seems that the root cause is that targets spawns new R processes, and the file backend keyring is not unlocked in these processes.

Do you see any way around this?

[gaborcsardi]

I don't understand what your issue is. To unlock a keyring, call the keyring_unlock() method and pass in the keyring and the unlock password.

[mattmoo]

Thanks, Gábor! To do that without interaction, would the password not have to be saved in plain text?

[gaborcsardi]

It does not have to be a string literal if that's what you are asking. You would obviously need a way to get the password to the subprocess. keyring does not do anything about this, it is up to targets and/or your application.