New bitwarden Beta Chrome extension requires a server-side flag

[yurividal]

Can this be enabled and used with vaultwarden?

More info here

[yurividal]

Feature flags need to be enabled, and these flags must be set:

```{
  "flagValues": {
    "extension-refresh": true,
    "unauth-ui-refresh": true
  }
}```

[BlackDex]

Not sure if there unauth-ui-refresh is needed, since Vaultwarden doesn't support that right now.

But the testing tagged containers do support the other.

[dfunkt]

Only the extension-refresh flag is needed.
Here's the API response from Bitwarden's servers when logging in using the beta extension:

{
    "version": "2024.10.0",
    "gitHash": "ad8aec97",
    "server": null,
    "environment": {
        "cloudRegion": "US",
        "vault": "https://vault.bitwarden.com",
        "api": "https://api.bitwarden.com",
        "identity": "https://identity.bitwarden.com",
        "notifications": "https://notifications.bitwarden.com",
        "sso": "https://sso.bitwarden.com"
    },
    "featureStates": {
        "display-eu-environment": true,
        "browser-fileless-import": false,
        "return-error-on-existing-keypair": true,
        "use-tree-walker-api-for-page-details-collection": false,
        "duo-redirect": true,
        "PM-5864-dollar-threshold": true,
        "enable-consolidated-billing": true,
        "AC-1795_updated-subscription-status-section": true,
        "email-verification": true,
        "anh-fcmv1-migration": true,
        "extension-refresh": true,
        "restrict-provider-access": true,
        "PM-4154-bulk-encryption-service": false,
        "vault-bulk-management-action": true,
        "bulk-device-approval": true,
        "ac-2059-member-access-report": true,
        "block-legacy-users": true,
        "inline-menu-field-qualification": true,
        "two-factor-component-refactor": false,
        "inline-menu-positioning-improvements": true,
        "ac-2833-provider-client-vault-privacy-banner": false,
        "pm-8285-device-trust-logging": true,
        "authenticator-2fa-token": true,
        "AC-2708-upgrade-password-manager-sub": true,
        "idp-auto-submit-login": true,
        "unauth-ui-refresh": false,
        "generate-identity-fill-script-refactor": true,
        "delay-fido2-page-script-init-within-mv2": true,
        "ac-1698-members-two-fa-query-optimization": true,
        "native-carousel-flow": false,
        "native-create-account-flow": false,
        "pm-10308-account-deprovisioning": false,
        "notification-bar-add-login-improvements": false,
        "AC-2476-deprecate-stripe-sources-api": false,
        "persist-popup-view": false,
        "cipher-key-encryption": false,
        "enable-new-card-combined-expiry-autofill": true,
        "storage-reseed-refactor": true,
        "PM-8163-trial-payment": false,
        "pm-3478-refactor-organizationuser-api": true,
        "remove-server-version-header": false
    },
    "settings": {
        "disableUserRegistration": false
    },
    "object": "config"
}

Notice that extension-refresh is enabled while unauth-ui-refresh isn't.

[a15355447898a]

Is there any new progress? I can't wait to use the New Bitwarden Beta Chrome extension

[BlackDex]

You can use it already with the latest stable version.

vaultwarden/.env.template

Line 350 in 38aad4f

## - "extension-refresh": Temporarily enable the new extension design until general availability (should be used with the beta Chrome extension)

Just enable that setting.

[fayeinmay]

I wondered if this is also available in Firefox with the latest extension version? using 2024.12.3 extension and 1.32.7 vaultwarden server. I activated the feature flag and logged out and in again in the extension, but the new UI is not being used. Any ideas to debug this?

[stefan0xC]

I had to log out and login again for the extension to load the /api/config endpoint with the enabled flags.

[BlackDex]

The clients seem to cache this for a long time. I had the same with the web-vault, i needed to delete the local storage values.

[fayeinmay]

Huh, I had to reinstall the extension for it to work now. Tried logging out and in again, tried deleting local storage values (extension storage).