* Staging: Vault Mgmt (#380) * Commit #1 - Updated Master Password article, and removed old versions (w/ redirects) - Repurposed Account Encryption Key Article - Moved Fingerprint Phrase article - Requisite re-ordering of security articles - Change "Account Mgmt" title to "Your Vault" - Slight change to "Import & Export" category title * - Managing Items - Favorites & Folders (+images) - Sync & Search (+images) - Import Export title change - Clarification re: Login v. Lock in "Field Guide to Two-step Login" - Clarifiation re: Org Invite Expiry in managing-users.md - New link to Acct. Encryption Key in encrypted-export.md * Commit #3 -Custom Fields - URIs (+ images) - File Attachments - VH Reports - Required re-ordering * Commit #4 -BWDC Login recommendation -VH Reports images - Added Two-step FAQs, Import FAQs - FAQ Nav Item depricated, targetting FAQs for each category are now the last article within respective categories * Commit #5 -Edit & move Account/Org Deletion Article -config.yml to re-order global nav -encrypted export update * General FAQs (preliminary edits) * Features > Misc. * return forgot-master-password.md & downstream order changes * delete account warning * fixed link
7.8 KiB
layout, title, categories, featured, popular, tags, order
| layout | title | categories | featured | popular | tags | order | |
|---|---|---|---|---|---|---|---|
| article | Directory Connector CLI |
|
true | false | 03 |
The Directory Connector CLI is suited toward work in environments where a desktop GUI is unavailable, or if you want to programmatically script directory sync operations using tools provided by the operating system (cron job, scheduled task, etc.). The Directory Connector CLI can be used cross-platform on Windows, macOS, and Linux distributions.
Getting Started
Complete the following steps to get started with the Bitwarden Directory Connector CLI:
-
Download the CLI from one of the following links:
-
Extract the
.zipand move the contents (bwdcandkeytar.node) to/usr/local/binor another directory in your$PATH. Please note,keytar.nodemust be in the same directory as the primarybwdcexecutable.Linux Only: If not already installed, install
libsecretwith your package manager of choice:apt-get install libsecret-1-0 brew install libsecretWindows Only: Windows users can add
bwdc.exeto the current user'sPATH{:target="_blank"}. -
Verify that the
bwdccommand works in your terminal by running the following:bwdc --help -
Connect Directory Connector to your Directory using the
bwdc config <setting> <value>command (see command reference). -
Configure Sync Options by editing your
data.jsonfile (to learn more, see [Directory Connector File Storage]({% link _articles/directory-connector/directory-sync-shared.md %})). Use thebwdc data-filecommand to obtain the absolute path of yourdata.jsonfile.Available Sync Options depend on the directory type in use, so refer to one of the following articles for a list of options available to you:
- [Sync with Active Directory or LDAP]({% link _articles/directory-connector/ldap-directory.md %})
- [Sync with Azure Active Directory]({% link _articles/directory-connector/azure-active-directory.md %})
- [Sync with G Suite (Google)]({% link _articles/directory-connector/gsuite-directory.md %})
- [Sync with Okta]({% link _articles/directory-connector/okta-directory.md %})
- [Sync with OneLogin]({% link _articles/directory-connector/onelogin-directory.md %})
-
Run the
bwdc testcommand to check whether your configuration would sync the expected results. -
Once your Directory and Sync Options are properly configured, and
bwdc testyields the expected results, run thebwdc synccommand to start a live sync operation.
Commands Reference
login
Use the login command to login to Directory Connector with your Bitwarden Account. You must be an Admin or Owner for your Organization to use Directory Connector (for more information, see [User Types and Access Controls]({% link _articles/organizations/user-types-access-control.md %})).
bwdc login [options] [email] [password]
Options include:
--method: Use this options to specify the [Two-step Login method]({% link _articles/two-step-login/setup-two-step-login.md %}) to use.0= Authenticator App1= Email3= YubiKey
--code: Use this option to specify the [Two-step Login]({% link _articles/two-step-login/setup-two-step-login.md %}) code for the specifiedmethod.--sso: Use this option to [Login with SSO]({% link _articles/login-with-sso/about-sso.md %}). Selecting this option will open the SSO Login Flow in your Web Browser. For more information, see [Access your Vault Using SSO]({% link _articles/login-with-sso/sso-access-your-vault.md %}).
For example:
{% callout warning %} Contrary to the following example, it's generally not recommended to enter your password inline, as this will save it to the history of the shell. Leaving the password out of the initial command will cause Bitwarden to prompt for it, which will not save it. {% endcallout %}
bwdc login bwuser@gmail.com mystrongpassword --method 0 --code 204678
logout
Use the logout command to logout of the Directory Connector CLI.
bwdc logout
help
The Bitwarden Directory Connector CLI is self-documented with --help content and examples for every command. List all available commands using the global --help option:
bwdc --help
Use the --help option on any specific command to learn more about that command:
bwdc test --help
bwdc config --help
test
The test command queries your directory and prints a JSON formatted array of groups and users that would be synced to your Bitwarden Organization whenever you run a real sync operation.
bwdc test
Use the --last option to test only the changes since the last successful sync.
bwdc test --last
sync
The sync command runs a live sync operation and pushes data to your Bitwarden Organization.
bwdc sync
Synced users and groups will be immediately available in your Bitwarden organization. Newly added users will receive an email invite to your Organization.
last-sync
The last-sync command returns an ISO 8601{:target="_blank"} timestamp for the last sync operation that was performed for users or groups. You must specify either users or groups as an <object> to run the command against:
bwdc last-sync <object>
Returns an empty response if no sync has been performed for the given object.
config
The config command allow you to specify your Directory settings:
bwdc config <setting> <value>
Options include:
server <server-url>directory <directory-type>ldap.password <password>azure.key <key>gsuite.key <key>okta.token <token>onelogin.secret <secret>
ldap.password, azure.key, gsuite.key, okta.token, and onelogin.secret can only be modified from the CLI using bwdc config, or from the [Desktop Application]({% link _articles/directory-connector/directory-sync-desktop.md %}).
data-file
The data-file command returns an absolute path to the data.json configuration file used by the Directory Connector CLI:
bwdc data-file
Configuration settings can be modified for the Directory Connector CLI by editing the data.json configuration file directly in your favorite text editor.
clear-cache
The clear-cache command allows you to clear cached data that the application stores while performing sync operations. For more information, see [Clear Sync Cache]({% link _articles/directory-connector/clear-sync-cache.md %}).
bwdc clear-cache
update
The update command allows you to check if your Directory Connector CLI is up-to-date:
bwdc update
If a newer version is found, the command will return a URL to download a new version. The Directory Connector CLI will not automatically update. You will need to use this URL download the new version manually.
{% callout warning %} If you using the CLI and Desktop App together, it is important to ensure their versions match whenever in use. Running two different versions may cause unexpected issues.
Check the version of the Directory Connector CLI using the --version global option.
{% endcallout %}
Troubleshooting
If you receive an error message referring to the libsecret shared object Error: libsecret-1.so.0: cannot open shared object file: No such file or directory, you may need to install libsecret which is required to store things securely on the host.