* SG-992 - Provider receives free org prompt when trying to auto scale org seats because plan type was missing and defaulting to free. PlanType has now been added to provider orgs returned as part of the profile sync. * SG-992 - Updated Stored proc name to match convention * EC-591 / SG-996 - (1) Update ProviderUserRepo.GetManyDetailsByProviderAsync to accept optional ProviderUserStatusType (2) Update OrganizationService.cs autoscaling user logic to check if an org is a provider org and send owner emails to the confirmed provider users instead of the managed org owners. Prevents scenario where newly created, managed orgs would not have an owner yet, and ownerEmails would be null and the email service would explode. * EC-591 / SG-996 - Remove comments * EC-591 / SG-996 - ES lint fix. * SG-996 - SQL files must have SQL extensions. * SG-996 / EC-591 - Update alter sql to be actually backwards compatible * SG-996 - Make Status actually optional and backwards compatible for ProviderUserUserDetails_ReadByProvider.sql * SG-992 - Update migrations to meet standards - (1) use CREATE OR ALTER and (2) Update view metadata after change if necessary * EC-591 / SG-996 - Update Stored Proc migration to use proper standards: (1) Remove unnecessary code and (2) Use CREATE OR ALTER instead of just ALTER * SG-992 / EC-591 / SG-996 - Refactor separate migrations into single migrations file per PR feedback * SG-992/SG-996 - Add SyncControllerTests.cs with basic test suite + specific test suite to ensure provider orgs have plan type mapped to output product type properly. * Fix lint issues by removing unnecessary using statements * SG-992 - Refresh of view metadata has to target the stored procs that reference the view -- not the view itself.
|1 day ago|
|.config||3 days ago|
|.git-hooks||5 months ago|
|.github||3 days ago|
|.vscode||3 months ago|
|bitwarden_license||3 days ago|
|dev||1 week ago|
|docker-unified||5 days ago|
|perf/MicroBenchmarks||1 week ago|
|scripts||2 months ago|
|src||1 day ago|
|test||1 day ago|
|util||1 day ago|
|.dockerignore||2 months ago|
|.editorconfig||1 week ago|
|.git-blame-ignore-revs||5 months ago|
|.gitattributes||1 year ago|
|.gitignore||1 year ago|
|CONTRIBUTING.md||8 months ago|
|Directory.Build.props||2 weeks ago|
|LICENSE.txt||2 years ago|
|LICENSE_BITWARDEN.txt||2 years ago|
|LICENSE_FAQ.md||6 months ago|
|README.md||3 days ago|
|SECURITY.md||11 months ago|
|bitwarden-server.sln||2 weeks ago|
The Bitwarden Server project contains the APIs, database, and other core infrastructure items needed for the "backend" of all bitwarden client applications.
The server project is written in C# using .NET Core with ASP.NET Core. The database is written in T-SQL/SQL Server. The codebase can be developed, built, run, and deployed cross-platform on Windows, macOS, and Linux distributions.
You can deploy Bitwarden using Docker containers on Windows, macOS, and Linux distributions. Use the provided PowerShell and Bash scripts to get started quickly. Find all of the Bitwarden images on Docker Hub.
Full documentation for deploying Bitwarden with Docker can be found in our help center at: https://help.bitwarden.com/article/install-on-premise/
These dependencies are free to use.
Linux & macOS
curl -s -L -o bitwarden.sh \ "https://func.bitwarden.com/api/dl/?app=self-host&platform=linux" \ && chmod +x bitwarden.sh ./bitwarden.sh install ./bitwarden.sh start
Invoke-RestMethod -OutFile bitwarden.ps1 ` -Uri "https://func.bitwarden.com/api/dl/?app=self-host&platform=windows" .\bitwarden.ps1 -install .\bitwarden.ps1 -start
Interested in contributing in a big way? Consider joining our team! We're hiring for many positions. Please take a look at our Careers page to see what opportunities are currently open as well as what it's like to work at Bitwarden.
Code contributions are welcome! Please commit any pull requests against the
master branch. Learn more about how to contribute by reading the Contributing Guidelines. Check out the Contributing Documentation for how to get started with your first contribution.
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. We also run a program on HackerOne.
No grant of any rights in the trademarks, service marks, or logos of Bitwarden is made (except as may be necessary to comply with the notice requirements as applicable), and use of any Bitwarden trademarks must comply with Bitwarden Trademark Guidelines.
Consider installing our git pre-commit hook for automatic formatting.
git config --local core.hooksPath .git-hooks
File Scoped Namespaces
We recently migrated to using file scoped namespaces to save some horizontal space. All previous branches will need to update to avoid large merge conflicts using the following steps:
- Check out your local Branch
git merge 9b7aef0763ad14e229b337c3b5b27cb411009792
- Resolve any merge conflicts, commit.
git merge -Xours 7f5f010e1eea400300c47f776604ecf46c4b4f2d
- Fix Merge conflicts