Skip to content

Platform independent 'API' to access the operating system's credential store. Currently supports: 'Keychain' on 'macOS', Credential Store on 'Windows', the Secret Service 'API' on 'Linux', and simple, platform independent stores implemented with environment variables or encrypted files. Additional storage back-ends can be added easily.

Platform independent API to many system credential store implementations. Currently supported:

  • Keychain on macOS,

  • Credential Store on Windows,

  • the Secret Service API on Linux, and

  • environment variables on other platforms.

Configuring an OS-specific backend

Query secret keys in a keyring

Each keyring can contain one or many secrets (keys). A key is defined by a service name and a password. Once a key is defined, it persists in the keyring store of the operating system. This means the keys persist beyond the termination of and R session. Specifically, you can define a key once, and then read the key value in completely independent R sessions.

Managing keyrings

A keyring is a collection of keys that can be treated as a unit. A keyring typically has a name and a password to unlock it.

Note that all platforms have a default keyring, and key_get(), etc. will use that automatically. The default keyring is also convenient, because the OS unlocks it automatically when you log in, so secrets are available immediately.

You only need to explicitly deal with keyrings and the keyring_* functions if you want to use a different keyring.


Maintainer: Gábor Csárdi

Other contributors:

  • Alec Wong [contributor]

  • Posit Software, PBC [copyright holder, funder]