872 Commits

Author SHA1 Message Date
renovate[bot]
ebe2148cfa [deps] AC: Update core-js to v3.51.0 (#24554)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2026-11-13 11:46:37 -05:00
Nick Krantz
09e5296b1e [PM-46898] fix: Use "My items" casing consistently (#24752)
* [PM-46898] fix: Name new My items collections with myItemsV2

The default user collection was named from the "myItems" key ("My Items"),
while the rest of the UI uses "myItemsV2" ("My items"). Switch the web,
browser, desktop and CLI paths that create the collection to "myItemsV2"
and drop the now-unused "myItems" key. Existing collections keep their
stored name.

* Use errorImportingMyItemsMultiCollectionV2 for the lowercase My items import error

* Label the My items shared folder from i18n in the vault table

* Label the My items shared folder from i18n in the item view and edit form

* Keep other members' emails on their My items collections and test the labels
2026-11-13 10:36:16 -06:00
Jared
4d76bbfb69 Feature flag is no longer required, keep code that is relevant to the feature flag being on. Revoke the rest (#24645) 2026-11-12 14:30:54 -05:00
Bernd Schoolmann
6b8ce54785 [PM-46036] perf(browser): Stop decrypting and caching the whole vault (#24277) 2026-11-12 03:35:37 +09:00
Vince Grassia
45e4aaae30 [BRE-2407] fix(cli): Choose bw update asset by license type and CPU architecture (#24658)
`bw update` picked the first release zip whose URL contained `bw-<os>`.
It ignored which build was running and the CPU architecture, so OSS users
were sent the commercial build and arm64 users were sent the x64 build.

- Add `licenseType` to the CLI ServiceContainer ("oss"), overridden to
  "bit" in the Bitwarden-licensed container, and pass it to UpdateCommand.
- Build the exact asset name, bw-{license}-{os}[-arm64]-{version}.zip,
  from the license, process.platform, process.arch and the release tag,
  and match it against asset names.
- Fall back to the release page when no matching asset exists or the
  OS/architecture has no published build.
- Type the GitHub release response and remove @ts-strict-ignore.

Depends on the bw-bit-* asset rename (BRE-2408).
2026-11-11 10:22:40 -05:00
Vince Grassia
5e1abff860 [BRE-2408] ci: Prefix commercial CLI artifacts with bw-bit- (#24652)
Commercial CLI zips were unprefixed (bw-linux-*, bw-macos-*, bw-windows-*)
while OSS zips use bw-oss-*. Set the commercial artifact_prefix to -bit so
both license types follow bw-{license}-{os}[-arm64]-{version}.zip, and point
the snap job and snapcraft.yaml at bw-bit-linux-*.
2026-11-11 09:52:03 -05:00
Patrik Svensson
88fa09626a [PAM-574] Vault: CipherService stops messaging the overlay (#24659) 2026-11-11 11:01:31 +01:00
Andy Pixley
0c7219337f Sign Windows builds with the win-code-signing managed identity over OIDC (#24656)
Based on #23917.

Co-authored-by: addisonbeck <github@addisonbeck.com>
2026-11-10 16:04:45 -05:00
Jared Snider
9b1d1f9365 Move SsoUrlService from libs/auth to libs/common (#24452)
* Move SsoUrlService from libs/auth to libs/common

Relocates SsoUrlService and DESKTOP_SSO_CALLBACK to a new
libs/common/src/auth/sso-url feature folder. Browser, desktop, and CLI now
import them from @bitwarden/common/auth/sso-url.

* Rename sso-url feature folder to sso-login
2026-11-09 15:35:22 -05:00
Jared Snider
bd4034b99a Move AuthRequestApiService from libs/auth to libs/common (#24453)
* Move AuthRequestApiService from libs/auth to libs/common

Relocates AuthRequestApiServiceAbstraction and DefaultAuthRequestApiService
to a new libs/common/src/auth/auth-request-api feature folder. Consumers now
import them from @bitwarden/common/auth/auth-request-api, which also removes
a restricted @bitwarden/auth/common import from DeviceManagementComponent.

* Rename auth-request-api feature folder to login-via-auth-request
2026-11-09 13:25:02 -05:00
adudek-bw
7f916b7d67 [PM-38256] Remove pm-30110-sdk-sends-api feature flag (#23913)
* [PM-38256] Remove pm-30110-sdk-sends-api feature flag

Remove the Pm30110SdkSendsApi feature flag and its checks so the SDK-backed
Send path is the only path.

- Drop the flag from the feature flag enum and defaults.
- Make Send decryption, key rotation and send push-notification sync
  SDK-only, and always run the pending Send deletion retry on sync.
- Always apply the 500 MB file Send size limit.
- Delete SendApiServiceSelector and fold SendSdkApiService into
  SendApiService. The merged class uses the SDK and makes REST calls itself
  for new-file save, cross-instance (apiUrl) access, and the read-back after
  each mutation.
- Remove getSend, getSends, putSendRemovePassword and deleteSend from the
  SendApiService abstraction; nothing outside the class called them.
- Inject the concrete SendApiService into ShareLinkService so share links
  keep resolving it.
- Update DI wiring and tests.

* [PM-38256] fix: Mock policiesByType$ in desktop send component spec

SendPolicyService now calls policiesByType$ unconditionally, so the
PolicyService mock must provide it.
2026-11-09 10:32:54 -05:00
adudek-bw
2fa9073746 [PM-42855] Rename Send removePassword/putSendRemovePassword to removeAuth (#23361)
* Rename Send removePassword/putSendRemovePassword to removeAuth (PM-42855)

The server collapsed the old password-only (V1) endpoint into remove-all-auth
(V2) logic a while back (server PR #6929 / PM-31497), so these methods remove
all auth on a Send today -- a password or an email-verification requirement
-- not just a password. Renames removePassword/putSendRemovePassword to
removeAuth/putSendRemoveAuth across SendApiService, SendSdkApiService,
SendApiServiceSelector, and every caller (DefaultSendFormService, send-details/
send-table/send-list components, web/desktop send components, the CLI's
internal call site), and corrects the matching user-facing copy that had the
same password-only framing bug.

Deliberately out of scope, left unchanged: the SDK's own remove_password
(WASM-exposed, a separate breaking change requiring its own SDK release), and
the CLI's public `remove-password` command name/class (SendRemovePasswordCommand)
-- only its internal call to the renamed service method was updated.

* [PM-42855] Show which kind of Send access control is being removed

Label the Send menu item, edit-page button, confirmation dialogs and success
toasts as "Remove password" or "Remove email verification" based on the
Send's authType, falling back to the generic wording when it is unknown. The
menu item now also appears for email-verified Sends.
2026-11-09 09:16:17 -05:00
github-actions[bot]
3716feec25 Bumped client version(s) (#24576)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-11-09 13:04:59 +00:00
Thomas Rittson
c5180132cb [PM-39833] Migrate POLICIES_NEW back to POLICIES (#24407)
Before this commit:
- POLICIES contains policies for confirmed organizations only, and is no longer used.
- POLICIES_NEW contains policies for accepted and confirmed organizations, and is used by policyService.

This commit copies POLICIES_NEW back to POLICIES; updates consumers to read from POLICIES; and drops POLICIES_NEW. This closes the loop so that we have a single state definition without the NEW suffix.
2026-11-06 09:05:33 +10:00
Bernd Schoolmann
15b3cc4f29 [PM-46030] Load non-SIMD SDK wasm when SIMD is unsupported (#24449) 2026-11-06 00:25:48 +09:00
Mike Amirault
07e71fbb83 [PM-37669] Remove flagged logic for Send Controls feature flags (#23849) 2026-11-04 21:28:51 +00:00
Aaron Jordan
c6ade9ab21 [PM-40202] [PM-40196] Aliases CLI collection items as shared-folder (#23897)
* [cli] aliases collection items as shared-folder

* [cli] add tests for org-shared-folder alias in edit and create

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* [cli] allow item-shared-folders in bw edit object validation

* [cli] add aliases in `delete` and `get template` methods as well

* [cli] document shared-folder aliases in CLI help text

* [cli] use the vfo1-foundation feature flag to control shared entity term

* [cli] filter terms based on flag for expected object text

* check flag value once up front

* [cli] rename sharedFolders var to useSharedFoldersTerm to express intent

* [cli] Update output terminology based on flag status

* [cli] add my-folder alias for folder objects, gated help text on flag

---------

Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-04 10:28:47 -08:00
Jordan Aasen
9b7a524468 [PM-40627] Remove pm-40201-derive-ssh-keys feature flag (#24298) 2026-11-04 10:26:24 -07:00
renovate[bot]
794728d215 [deps] Tools: Update papaparse to v5.7.0 (#23512)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2026-11-03 12:46:38 -08:00
Andreas Coroiu
b4b11d8d5d [PM-42408] feat: Push lock and logout from LockService and LogoutService (#23880)
* [PM-42408] feat: Push lock and logout from LockService and LogoutService

Lock clears the SDK client's in-memory user key before USER_KEY is wiped,
so the client can't do crypto while the account is already reported as
locked. Logout disposes the client before the logout broadcast.

* Explain why the SDK client locks before the caches are cleared
2026-11-03 09:12:22 +01:00
vchauhan-bitwarden
41f307c001 [PM-45197] refactor: Move provider domain into libs/common/src/provider (#24257)
* [PM-45197] refactor: Move provider domain into libs/common/src/provider

* [PM-45197] refactor: Add barrel export for libs/common/src/provider Add libs/common/src/provider/index.ts and import provider types from
@bitwarden/common/provider outside libs/common, so the folder can move
again without touching every consumer. The service implementations stay
out of the barrel because the abstraction and the implementation are
both named ProviderService. Code inside libs/common keeps relative
imports to avoid circular imports. No behavior change.
2026-10-30 20:55:14 +05:30
Jared Snider
cb5d262617 PM-46016 - Move LogoutService from libs/auth to libs/common/src/auth/logout (#24275)
Moves LogoutService, DefaultLogoutService, LogoutReason, and NewActiveUser to libs/common/src/auth/logout so libs/common code can depend on them. Updates all imports to @bitwarden/common/auth/logout and removes the no-restricted-imports suppressions that libs/common needed to import them from libs/auth. No behavior change.
2026-10-29 20:34:53 +00:00
Shane Melton
818548aa3f [PAM-336] Vault: edit, attach and delete for restricted ciphers (#24077) 2026-10-26 13:49:49 -07:00
Maciej Zieniuk
cd44cba2cf fix(logging): Performance marks and measures grow without limit (#24136)
* fix(logging): Performance marks and measures grow without limit

Marks and measures are recorded whether DevTools is open or not, and nothing clears them. When the app stays open for days, locked or unlocked with the session timeout set to "Never", they might use hundreds of megabytes of memory.

* simplifications
2026-10-26 15:00:06 +01:00
Andreas Coroiu
c609e67180 [PM-42403][PM-42406] feat: Push unlock and organization keys ahead of their state writes (#23879)
* [PM-42403] refactor: Extract KeyService.toUserEncryptedOrgKeys

Pushing organization keys into a long-lived SDK client needs the same
conversion that encryptedOrgKeys$ does, from paths that hold the user's
private key directly. Pull it into a helper that takes the private key and
provider keys as arguments, and cover encryptedOrgKeys$ with tests.

* [PM-42406] feat: Push unlock and organization keys ahead of their state writes

Unlock tries the long-lived SDK client first and falls back to the
register client when there is none. After every unlock, and whenever
organization keys change, KeyService pushes the user-encrypted
organization keys to SdkService before they are written to state.
Organization keys cross into SdkService as the SDK's UnsignedSharedKey,
converted from EncString in KeyService. Building the payload never fails
an unlock or a sync.

* Remove dead guard from toUserEncryptedOrgKeys

* Test buildSdkUnlockData with no stored organization keys

* refactor: Signal unlock with a boolean and read the user key from state

* refactor: Return the unlocked SDK client from unlock instead of a boolean
2026-10-26 13:00:19 +01:00
Jordan Aasen
3e27b66cba [PM-44239] deps: Update multer to 2.4.0 (#24073)
Resolves GHSA-3pph-fpjx-jg34 (orphaned diskStorage files on aborted uploads).
2026-10-22 16:16:54 -07:00
Bernd Schoolmann
60694f7d0a Skip CLI storage writes that change nothing (#23957)
Each save rewrites the whole data.json, ~19 MB with a large vault, and
`bw get item` saved two values that were already stored. Compare the
stored JSON first and skip the write when it would not change. The
update is still emitted, as before.
2026-10-21 20:50:22 +09:00
Bernd Schoolmann
0a9757ce28 Copy cached CLI storage values with a JSON copy (#23956)
The storage cache returns a copy on every get, and a command reads the
whole ciphers value (~16 MB for a large vault) at least once.
structuredClone took ~22 ms for it. The cache only ever holds plain JSON,
so a direct recursive copy gives the same result in ~6 ms.
2026-10-21 20:50:21 +09:00
Bernd Schoolmann
309b1f7530 Re-read CLI storage only when data.json changed (#23955)
Every storage read parsed the whole data.json. A single `bw get item`
reads storage 57 times, and with a large vault the file is ~19 MB, so
parsing it again dominated the command.

Keep the parsed contents and re-read only when the file's inode, size,
mtime or ctime show another process changed it. Values are copied on
get and stored as their JSON round-trip on save, so callers see exactly
what a re-read from disk used to return.
2026-10-21 20:50:21 +09:00
Bernd Schoolmann
0015108d55 [PM-45308] perf(cli): Take the storage file lock synchronously (#23954)
* Take the CLI storage file lock synchronously

Every storage access takes a cross-process lock on data.json. It was
acquired asynchronously, so concurrent accesses within one process
found the lock held by their own process and backed off 100-250 ms
each; 10 concurrent reads scheduled 45 backoffs.

The storage actions are synchronous, so take the lock with lockSync and
lock, act and release in one synchronous step. No other access of this
process can run while the lock is held, so it never waits for itself.
Only another process holding the lock still makes it wait, with the
same backoff as before.

* Remove unused @types/retry dependency

The retry import was dropped when the storage lock became
synchronous. Nothing references the types directly anymore.
2026-10-21 20:50:21 +09:00
Bernd Schoolmann
0355076f87 [PM-45308] perf(cli): Exit once a command has finished (#23953)
* Exit the CLI once a command has finished

After printing its output, every command left the process idle until
leftover timers expired: the desktop IPC discovery timeout and RxJS
intervals kept the event loop alive for ~1.7 s per invocation.

Exit explicitly after the command's action resolves, except for serve,
which keeps running. stdout and stderr are flushed first, since a pipe
is asynchronous on macOS and exiting straight away could truncate
large output.

* Let serve stay pending until it stops

Replace the LONG_RUNNING_COMMANDS allowlist. serve now resolves when
its server closes or errors, so every command exits the same way:
the action resolves, then the CLI flushes and exits.

Await the export event collection and the import sync. The forced
exit could otherwise cut them short.

* Restore serve.command spec

An earlier commit overwrote the existing serve.command spec. Restore
it and move the untilStopped tests to their own spec.
2026-10-21 20:50:20 +09:00
Bernd Schoolmann
882b8e571f Add CLI end-to-end performance harness (#23952)
Times the prod build of bw as a user runs it: time to first output and
time to process exit, per command, in interleaved rounds across variant
worktrees. Each variant logs in to its own data dir during untimed
setup, and every run's output is checked so a failing command is never
measured as fast.
2026-10-21 20:50:20 +09:00
Jordan Aasen
1f0f20e130 [PM-28207] Remove pm-28192-cipher-attachment-ops-to-sdk feature flag (#23902) 2026-10-20 10:27:03 -07:00
adudek-bw
6b14f423fb [PM-42819] Route CLI cross-instance Send receive through SendReceiveClient (#23714)
* [PM-42819] Route CLI cross-instance Send receive through SendReceiveClient

Build a receive-scoped SDK client pointed at the Send link's server instead
of reintroducing a generic ephemeral client on SdkService. Gated behind
pm-30110-sdk-sends-api; same-instance receives are unchanged.

* [PM-42819] Mint cross-instance Send access tokens through SendReceiveClient

Run the whole cross-instance receive flow (token minting, password hashing,
email/OTP exchange, access, download, decrypt) through the receive-scoped SDK
client so nothing touches the signed-in instance. Pass the device identifier
and CLI user agent to the SDK client. Legacy path is unchanged when the flag
is off or the Send is on the configured server.

* [PM-42819] Use NotFound SDK variant and share send access token helpers

Detect a missing Send in the CLI receive command via the SDK's NotFound
variant instead of matching the error message. Move the SDK credential and
token-error helpers into libs/common send-access utils shared by
DefaultSendTokenService and the receive command.

* [PM-42819] Update sdk-internal to 0.2.0-main.1127

Pick up SendReceiveClient and the NotFound error variant from the merged
sdk-internal PR (bitwarden/sdk-internal#1586).
2026-10-19 10:09:47 -04:00
github-actions[bot]
7b8412a52d Bumped client version(s) (#23963)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-10-19 08:49:44 -04:00
bmbitwarden
124f1b1d21 PM-42722 resolved unbounded kdf parameters (#23039)
* PM-42722 resolved unbounded kdf parameters

* PM-42722 resolved pr comment re: defining a separate constant

* PM-42722 resolve pr comments

* PM-42722 passing unit tests

* PM 42722 reverted spec change
2026-10-16 13:12:39 -04:00
Dmitry Yakimenko
67954962aa [PM-44451] Add 1Password direct import through the SDK on desktop and in the extension (#23627)
* Add 1Password direct import through the SDK on desktop and in the extension

* Apply the design feedback to the 1Password direct importer

* Keep the 1Password prompts open on a click outside or Escape

* Drop the desktop CORS header rewrite for 1Password

* Trim the 1Password importer tests to the ones that check logic

* Test the 1Password form rules directly and drop the overlapping specs

* Check for an org import without a collection before the 1Password prompts open

* Drop the null toast title from the 1Password importer

* Show a refused 1Password Secret Key and password in a toast

* Tell a 1Password account that signs in only with SSO before asking for its password

* Tell the user to check a 1Password email that 1Password refuses as malformed

---------

Co-authored-by: John Harrington <84741727+harr1424@users.noreply.github.com>
Co-authored-by: Alex Dragovich <46065570+itsadrago@users.noreply.github.com>
2026-10-16 09:01:30 -07:00
Nick Krantz
928f0440c4 [PM-34414] Remove pm-34410-attachment-upload-progress feature flag (#23604)
* [PM-34414] refactor: Always use progress-aware Azure attachment upload path

pm-34410-attachment-upload-progress is always true in production, so
AzureFileUploadService no longer needs to branch on it. Removes the
dead legacy (non-progress) upload path and the now-unused ConfigService
dependency, cascading through FileUploadService and its construction
sites.

* Always pass upload progress options through cipher attachment upload

* Remove unused pm-34410-attachment-upload-progress feature flag

* Check response status on progress-reporting attachment upload

ApiService.postAttachmentFile's XHR branch (used whenever onProgress is
set) never checked the response status before returning, unlike the
send() fallback and the Azure upload paths. A failed Direct (self-hosted)
attachment upload would resolve successfully with no thrown error, so
CipherFileUploadService never rolled back and the UI showed a false
success toast. Now always passing upload options through (PM-34414)
makes onProgress unconditional for these uploads, so this latent bug
needed fixing alongside it.

* Propagate XHR response headers so attachment upload errors keep server message

* [PM-34414] Guard XHR attachment upload against insecure API URLs

Add the same https:// check that fetch() enforces before calling
nativeXMLHttpRequest in postAttachmentFile, so bearer tokens are
not sent over plaintext HTTP for self-hosted users with http:// API URLs.

Add a test to assert InsecureUrlNotAllowedError is thrown and that
nativeXMLHttpRequest is never called when the API URL is insecure.
2026-10-15 15:45:18 -05:00
Andreas Coroiu
4f702cc498 [PM-42405] feat: Push feature flags from ConfigService.renewConfig (#23867)
A long-lived SDK client keeps the feature flags it was given, so
ConfigService pushes them on every per-user config renewal, before the
new config is written to state. The manual-DI apps construct SdkService
(and the AppIdService it needs) before KeyService and ConfigService so
both can depend on it.
2026-10-15 16:52:47 +02:00
Bernd Schoolmann
474596bee2 [PM-44494] fix(biometrics): fix biometric id update enrollment despite failed biometrics (#23646) 2026-10-15 20:57:41 +09:00
Andreas Coroiu
73246fb5ce [PM-42402] refactor: Resolve SdkService's cycle-forming dependencies lazily (#23861)
KeyService and ConfigService will take SdkService as a dependency, and
ApiService already reaches it at runtime through VaultTimeoutSettingsService
and KeyService. Taking those services as thunks lets SdkService be injected
into them without closing a construction cycle.
2026-10-15 13:41:21 +02:00
Todd Martin
93832cc349 [PM-28650] Add logout reason in all remaining cases (#23317)
* Initial changes.

* Route direct logout paths through LogoutService and log callback logouts

Converts every direct messagingService.send("logout") site to
logoutService.logout(userId, reason). Introduces the reasons the new
sites needed: userInitiated, deauthorizedSessions, emailChanged,
kdfChanged, tooManyInvalidPinAttempts, keyConnectorError (existing).

Two paths cannot inject LogoutService and carry the reason on the message
payload instead: AccountService.delete (libs/common cannot depend on
libs/auth) and the Electron main-process menu (main process has no
Angular DI). LOGOUT_CALLBACK factory now logs the reason so
TokenService, SyncService, ServerNotifications, KeyConnector, and
ApiService paths get the same log line. Deletes an unreachable logOut
method from DefaultLoginDecryptionOptionsService.

* Log logout reason in browser background service worker

The browser background context wires its own logoutCallback into
TokenService, KeyConnectorService, SyncService, and
ServerNotificationsService. That callback bypassed the Angular DI
LOGOUT_CALLBACK factory that logs the reason, so background auth-failure
logouts (invalid access token, refresh-token retrieval failure,
key-connector error, sync-triggered accountDeleted or invalidSecurityStamp,
server logoutNotification) had no diagnostic log line.

Same one-line info log now fires at the callback entry, matching the
Angular factory.

* Assert new LogoutReason at each converted callsite in unit tests

Adds explicit expect(logoutService.logout).toHaveBeenCalledWith(userId, reason)
assertions to seven specs that were touched by the reason conversions but
did not verify the reason string. Prevents silent regressions if a reason
value is renamed or a callsite is refactored without updating the log.

Coverage added:
- AccountSecurityComponent logOut: userInitiated (or none when cancelled)
- ChangeEmailComponent submit: emailChanged
- ChangeKdfConfirmationComponent submit: kdfChanged (updates existing
  messagingService.send assertion)
- UserKeyRotationService rotate paths: userKeyRotation (SDK and TypeScript
  paths)
- LoginDecryptionOptionsComponent: missingEmailError on missing email,
  userInitiated on user-cancelled logout dialog
- KeyRotationDialogService: userKeyRotation on all three rotation paths
- LockComponent: userInitiated on user log-out, noUnlockOptionsAvailable
  on the fallback when no unlock options are available

* Fixed test input.

* Fixed incorrect "expired" property on msg.

* Made sure to get the right userId

* Add unit tests for logout-reason threading

Locks in behavior of the callers converted in this PR:

- RuntimeBackground.processMessage forwards `msg.logoutReason` (and
  `msg.userId`) to `MainBackground.logout`. Guards against a
  regression to the stale `msg.expired` field the prior code read.
- DefaultOrganizationInviteService passes
  `"masterPasswordPolicyEnforcement"` when the MP-policy detour logs
  the user out, on both `validateAndAcceptDirectOrgInvite` and
  `acceptOpenOrgInvite`.
- AccountMenuComponent passes `"userInitiated"` when the user hits
  the logout menu item.
- DeauthorizeSessionsComponent posts the security stamp then routes
  through `LogoutService.logout(userId, "deauthorizedSessions")`
  instead of the fire-and-forget `messagingService.send("logout")`.

* Drop unused MessagingService constructor dependency

`change-password.component.ts` and `set-initial-password.component.ts`
switched their sole `messagingService.send("logout")` call over to
`logoutService.logout(userId, ...)` earlier in this PR, leaving
`private messagingService: MessagingService` as a declared-but-unread
parameter property. The workspace has `noUnusedLocals` off and the
lint rule ignores unused parameter properties, so the compiler doesn't
catch it — every consumer still has to satisfy the dependency.

Removes the parameter and its import from both components, matching
the same cleanup this PR performed for
`DefaultLoginDecryptionOptionsService`/`WebLoginDecryptionOptionsService`.

* fix: prettier on account-menu.component.spec.ts

* Fixed test.

* Add missing log on app logout.

* Remove obsolete logout reason for KDF change.
2026-10-13 10:50:45 -04:00
John Harrington
d1e25b7e99 [PM-42643 ] Tools-owned URL validation (#23160)
* initial remediation with escape hatch

* update per design specs

* replace joined clause with single sentence
2026-10-09 14:47:42 -07:00
Jonathan Prusik
f2cd9086e1 [PM-44316] Harden basic auth responses (#23585)
* limit scenarios in which a basic auth challenge is automatically responded to

* constrain responses to challenges by allowlisted subresource types

* additional adjustments for Firefox

* further exclude subresources entirely from auth challenge response

* catch source errors

* ensure the user basic auth setting is rechecked upon account switch

* move the basic auth resolved state up to the autofill settings service

* skip basic auth for Safari
2026-10-09 09:47:17 -04:00
Bernd Schoolmann
ae828b43c2 [PM-44108] perf: Add performance measurements to unlock and sync (#23476) 2026-10-06 16:22:21 +00:00
Maciej Zieniuk
c3cb584330 Remove enroll-aead-on-key-rotation feature flagged code (#23671) 2026-10-06 09:48:18 +00:00
Jared
915ac1e9b4 [PM-38906] bulk decrypt collections with failures unstacked (#22886)
* Bulk decrypt with decrypt with failures new PR

* Implements rename feature for when a collection fails decryption via SDK call

* PR comments actioned on

* PR claude comment fixes

* PR claude comment fixes

* PR claude comments fixed

* PR Claude Comment fixes

* Rid of unused signal

* Fix up PR comments from Thomas

* Updates feature flag to proper key from epic

* Fix PR claude finding 1

* PR Claude comment fixes

* Fix PR comments

* Fix up message

* Rids of error badge in table to go back to existing behavior since no design/product capacity right now. Also rids of warning box above name of broken collection name
2026-10-05 13:58:27 -04:00
Bernd Schoolmann
8172202eb5 fix(biometric-ipc): Address the CLI as its own IPC endpoint (#23275) 2026-10-05 23:09:23 +09:00
github-actions[bot]
b40c27d892 Bumped client version(s) (#23647)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-10-05 08:56:04 -04:00
Jared Snider
78f27a584a Tools/PM-44409 - CLI - Send Receive command - Add Device Identifier Header to send access token request (#23607)
* PM-44409 - Provide AppIdService to SendReceiveCommand

* PM-44409 - Send device identifier on direct Send access token requests
2026-10-01 16:21:20 -04:00