* do not purge ciphers in the default collection
* Update `DeleteByOrganizationId` procedure to be more performant based on PR review feedback
* update EF integration for purge to match new SQL implementation
* update Cipher_DeleteByOrganizationId based on PR feedback from dbops team
* Added MasterPasswordUnlock to UserDecryptionOptions as part of identity response
* Implement support for authentication data and unlock data in kdf change
* Extract to kdf command and add tests
* Fix namespace
* Delete empty file
* Fix build
* Clean up tests
* Fix tests
* Add comments
* Cleanup
* Cleanup
* Cleanup
* Clean-up and fix build
* Address feedback; force new parameters on KDF change request
* Clean-up and add tests
* Re-add logger
* Update logger to interface
* Clean up, remove Kdf Request Model
* Remove kdf request model tests
* Fix types in test
* Address feedback to rename request model and re-add tests
* Fix namespace
* Move comments
* Rename InnerKdfRequestModel to KdfRequestModel
---------
Co-authored-by: Maciej Zieniuk <mzieniuk@bitwarden.com>
* feat: add static enumeration helper class
* test: add enumeration helper class unit tests
* feat: implement NeverAuthenticateValidator
* test: unit and integration tests SendNeverAuthenticateValidator
* test: use static class for common integration test setup for Send Access unit and integration tests
* test: update tests to use static helper
If a user approves an invalid auth request, on the Requesting Device they currently they get stuck on the `LoginViaAuthRequestComponent` with a spinning wheel.
This PR makes it so that when an Approving Device attempts to approve an invalid auth request, the Approving Device receives an error toast and the `UpdateAuthRequestAsync()` operation is blocked.
* Use single method for default collection creation
* Use GenerateComb to create sequential guids
* Pre-sort data for SqlBulkCopy
* Add SqlBulkCopy options per dbops recommendations
* feat(policies): add URI Match Defaults organizational policy
Signed-off-by: Ben Brooks <bbrooks@bitwarden.com>
* feat(policies): remove unecessary model and org feature
Signed-off-by: Ben Brooks <bbrooks@bitwarden.com>
---------
Signed-off-by: Ben Brooks <bbrooks@bitwarden.com>
* fix(pending-auth-request-view): [PM-25453] Bugfix Auth Requests Multiple Users Same Device - fixed view to allow for multiple users for each device when partitioning for the auth request view.
* Refactor license date calculations into extensions
* `dotnet format`
* Handling case when expirationWithoutGracePeriod is null
* Removed extra UseAdminSponsoredFamilies claim
* feat: modify current context to not include user information
* fix: circular dependency for feature check in current context. Successfully tested client isn't affected with feature flag off.
* test: whole bunch of tests for current context
* Remove external loadImpact option that is being replaced by DataDog
* Add load test workflow
Keep otel encrypted, but skip verification
Go back to what was working from Billing-Relay
Tune test configuration based on last test output.
Tune config loadtest
Tune tests a bit more by removing preAllocatedVUs
Revert "Tune tests a bit more by removing preAllocatedVUs"
This reverts commit ab1d170e7a3a6b4296f2c44ed741656a75979c80.
Revert "Tune config loadtest"
This reverts commit 5bbd551421658e8eb0e2651fb1e005c7f1d52c99.
Tune config.js by reducing the amount of pAV
Revert "Tune config.js by reducing the amount of pAV"
This reverts commit 1e238d335c27ebf46992541ca3733178e165b3aa.
Drop MaxVUs
* Update .github/workflows/load-test.yml
Co-authored-by: Matt Bishop <mbishop@bitwarden.com>
* Fix newline at end of load-test.yml file
* Fix github PR accepted code suggestion
---------
Co-authored-by: Matt Bishop <mbishop@bitwarden.com>
