Set three new license options to true: UseRiskInsights, UseOrganizationDomains, and UseAdminSponsoredFamilies.
As mentioned in #229, licenses had to be regenerated starting in 2025.5.0. It looks like new options were added which default to false unless we set them to true here. I am not sure if the version needs to be bumped or not. I tested locally and I can now access the Claimed Domains page in my organization.
Signed-off-by: Joseph Gigantino <128943406+Jgigantino31@users.noreply.github.com>
* Update build.sh to reflect move to GHCR
* Update build.ps1 to reflect move to GHCR
* Update README.md to reflect move to GHCR
* Update Dockerfile-bitwarden-patch to reflect move to GHCR
* Updated license version to 12, added SM options, increased max seats (short to int) (#172)
* - Updated license version to 12
- Added new SM license options
* Change seats, smseats, smserviceaccounts from short to int, like they are in the Bitwarden server code, to allow for the accurate maximum amount of seats
* Add extra ignore
* Code cleanup
* Ignore more VS cruft
* Bring up to date with upstream
(Update License to use Secrets Manager fully)
* Update to .NET 8.0
* Initial work
* Fix typo
* Fix typo
* Fix stupid issue
* Add comments and fix minor issues
* Add extra information
* Add Linux script for generating keys
* Add circleci
* Add comments
* Add extra option
* Add missing permissions and empty script for now
* Fix line endings
* Add missing mount point
* Simplify patch
* Fix scripts
* Reduce complexity
* Fix circleci
* Remove useless line
* Move to src folder and improve image creation
* BitBetter: update build.sh / update-bitwarden.sh
Bitwarden has changed the way they report version numbers for
self-hosted installations.
Fixes https://github.com/jakeswenson/BitBetter/issues/134
Credit to @Ayitaka for the fix
Tested and Verified, Updated install to 1.47.1
Signed-off-by: Donald Hoskins <grommish@gmail.com>
* Update build.sh
Remove extraneous comment
* update-bitwarden.sh: Fix relative path
update-bitwarden.sh attempted to update BitBetter via
./build.sh, but if run via crontab, you aren't in
the BitBetter directory.
Fixed to find it correctly.
Signed-off-by: Donald Hoskins <grommish@gmail.com>
* Update update-bitwarden.sh
Co-authored-by: h44z <christoph.h@sprinternet.at>
Co-authored-by: h44z <christoph.h@sprinternet.at>
* Use latest release of bitwarden as base image (#67, #66)
* Add a script which simplifies Bitwarden updates
* fix typo
* Add UseApi
* Updated version, created update section
* Workaround for docker-compose --ignore-pull-failures bugs (4377 and 7127)
* use version from docker script
* check if bitbetter images are outdated
Co-authored-by: Lework <kuailemy123@163.com>
Co-authored-by: Jake Swenson <jakeswenson@users.noreply.github.com>
Co-authored-by: Jeff Alyanak <jeff@alyanak.ca>
* Exclude cert.cert from git
* Use latest release of bitwarden as base image (#67, #66)
* Add a script which simplifies Bitwarden updates
* fix typo
* Add UseApi
* Updated version, created update section
* Workaround for docker-compose --ignore-pull-failures bugs (4377 and 7127)
* use version from docker script
* check if bitbetter images are outdated
* Make Sso available in org license
Add `UseSso` var and enable
* Update README.md
Co-authored-by: Christoph Haas <christoph.h@sprinternet.at>
Co-authored-by: Lework <kuailemy123@163.com>
Co-authored-by: Captainhook <ec14018@qmul.ac.uk>
