Directory Connector File Storage
The desktop app and CLI share a database and configurations, so simultaneous use on a single machine is not recommended. The recommended path is to complete configuration and testing using the desktop app, and subsequently using the CLI to schedule automatic syncing to your production organization.
We recommend using the desktop app or CLI prior to conditioning the Directory Connector configuration file, as it is not possible to setup the entirety of Directory Connector from this file. Authentication values, like keys or secrets, must be set from either the desktop app or CLI.
The Directory Connector configuration file (
data.json) can contain the following properties which you may directly edit in order to set the connection to your directory and and sync options:
data.jsonfile will also contain properties that should not be manually edited in the file. Only manually edit the properties described in the following table.
Avoid opening or modifying
data.json while the Directory Connector desktop app or CLI executable is running.
The location of
data.json depends on which platform is in use:
%AppData%\Bitwarden Directory Connector
~/Library/Application Support/Bitwarden Directory Connector
~/.config/Bitwarden Directory Connector
Using the Directory Connector CLI, run the
data-file command to discover the absolute path to the
If a secure storage environment is not available, you can configure the Directory Connector CLI to use plaintext storage of secrets. To do so, set the following environment variable to override secure storage, for example by running
sudo -H gedit /etc/environment:
With plaintext storage enabled, you can then configure all settings directly, in plaintext, from the
data.json configuration file.
Plaintext storage of secrets is not compatible with the Directory Connector desktop app. You should only use the Directory Connector CLI with plaintext storage of secrets.