* Refactor: Remove ConfigService dependency from auto-confirm related components - Eliminated ConfigService from MainBackground, AutoConfirmPolicy, UserLayoutComponent, WebVaultPromptService, and organizationPolicyGuard. - Updated logic to directly use organization properties instead of feature flags for auto-confirm functionality. - Adjusted tests in DefaultAutomaticUserConfirmationService to reflect the removal of feature flag checks. - Cleaned up unused imports related to ConfigService across various files. * Refactor: Update date handling in tests and remove unused feature flag checks - Changed date calculation in WebVaultExtensionPromptService tests to use milliseconds for accuracy. - Removed unused feature flag checks from WebVaultPromptService tests, simplifying the logic and improving clarity. * Refactor: Update organizationPolicyGuard to include ConfigService in feature callback - Modified the organizationPolicyGuard to accept ConfigService as an additional parameter in the feature callback. - Adjusted the SendComponent route to align with the updated guard implementation. * Fix: Adjust date calculation in WebVaultExtensionPromptService tests for accuracy - Updated the test to set the exact date to 30 days prior using setDate method for clarity and to avoid potential issues with DST boundaries. |
||
|---|---|---|
| .. | ||
| src | ||
| eslint.config.mjs | ||
| jest.config.js | ||
| package.json | ||
| project.json | ||
| README.md | ||
| test.setup.ts | ||
| tsconfig.eslint.json | ||
| tsconfig.json | ||
| tsconfig.lib.json | ||
| tsconfig.spec.json | ||
Automatic User Confirmation
Owned by: admin-console
The automatic user confirmation (auto confirm) feature enables an organization to confirm users to an organization without manual intervention from any user as long as an administrator's device is unlocked. The feature is enabled via the following:
- an organization plan feature in the Bitwarden Portal (enabled by an internal team)
- the automatic user confirmation policy in the Admin Console (enabled by an organization admin)
- a toggle switch in the extension's admin settings page (enabled on the admin's local device)
Once these three toggles are enabled, auto confirm will be enabled and users will be auto confirmed as long as an admin is logged in. Note that the setting in the browser extension is not synced across clients, therefore it will not be enabled if the same admin logs into another browser until it is enabled in that browser. This is an intentional security measure to ensure that the server cannot enable the feature unilaterally.
Once enabled, the AutomaticUserConfirmationService runs in the background on admins' devices and reacts to push notifications from the server containing organization members who need confirmation.
For more information about security goals and the push notification system, see README in server repo.