GitHub-Bitwarden
/
directory-connector
mirror of https://github.com/bitwarden/directory-connector.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
A tool for syncing a directory (AD, LDAP, Azure, G Suite, Okta) to an organization.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
135 Commits
40 Branches
57 Tags
178 MiB
 
 
 
 
Tree: 598db5c83b
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '598db5c83b'
${ noResults }
Kyle Spearrin 598db5c83b
add organization duo 2fa type 		8 years ago
src add organization duo 2fa type 8 years ago
.gitattributes stub out projects for the solution 9 years ago
.gitignore stub out projects for the solution 9 years ago
LICENSE Initial commit 9 years ago
README.md Uppercase Bitwarden 8 years ago
SECURITY.md Uppercase Bitwarden 8 years ago
bitwarden-directory-connector-noinstaller.sln remove gui app 8 years ago
bitwarden-directory-connector.sln update libs. convert service to new csproj format 8 years ago

README.md

appveyor build Join the chat at https://gitter.im/bitwarden/Lobby

Bitwarden Directory Connector

The Bitwarden Directory Connector is a command line application used to connect your Bitwarden enterprise organization to an existing directory of users and groups. It is written in C# with the .NET Framework. It consists of a console application and an optional windows service to run syncs in the background on a specified interval.

Supported directories:

  • Active Directory
  • Azure Active Directory
  • GSuite (Google)
  • Any other LDAP-based directory

Build/Run

Requirements

Open bitwarden-directory-connector.sln or bitwarden-directory-connector-noinstaller.sln. After restoring the nuget packages, you can build and run the application.

Contribute

Code contributions are welcome! Visual Studio is required to work on this project. Please commit any pull requests against the master branch.

Security audits and feedback are welcome. Please open an issue or email us privately if the report is sensitive in nature. You can read our security policy in the SECURITY.md file.