Type of change

• Bug fix
• New feature development
• Tech debt (refactoring, code cleanup, dependency upgrades, etc)
• Build/deploy pipeline (DevOps)
• Other

Objective

With 1Password changing their export format from .1pif to .1pux in recent versions, this adds an importer to import 1pux into Bitwarden.

The 1pux format is essentially a zip archive including multiple files. The initial one of interest is the export.data file which contains the vault data.

Further information about the new 1pux format can be found here: https://support.1password.com/1pux-format/

Rough overview of imported ciphers/fields:

• Trashed items are ignored

• Empty fields are skipped

• Login items

  • Username
  • Password
  • TOTP
  • Password history

• CreditCard items

  • Cardholder
  • CC Number
  • CVV
  • Expiry date
  • Card brand is set using CC Number and only to our supported brands

• Identity items

  • Firstname
  • Initial
  • LastName
  • DefaultPhone
  • Company
  • Email
  • Username
  • Address

• Import of custom fields (loginfields and sections) for all CipherTypes

  • Fields marked as Date are saved as Unix Epoch and are converted to UTC string

• Favorites are set

• Import into folders based on the first entry in tags

• Import into collection based on the first entry in tags, if the import is ran from within an organization

• Folder and Collection names are captialized

• Category Mappings
  1password supports various categories (Item types) which are saved in categoryUuid and are mapped as the following:

• Bitwarden Login Type:

  • Login
  • Database
  • Password
  • WirelessRouter
  • Server
  • API Credentials

• Bitwarden CreditCard Type:

  • CreditCard
  • BankAccount

• Bitwarden Secure Note:

  • SecureNote
  • SoftwareLicense
  • EmailAccount
  • MedicalRecord

• Bitwarden Identity Type:

  • Identity
  • DriversLicense
  • OutdoorLicense
  • Membership
  • Passport
  • RewardsProgram
  • SocialSecurityNumber

1pux is prepared for including attachments but as of now, they are not included. This will be handled at a later point when 1password has added this feature.

Asana task: https://app.asana.com/0/1153292148278596/1201437354678085/f

Code changes

• common\src\importers\onepasswordImporters\types\onepassword1PuxImporterTypes.ts: Added types definitions for the export.data file
• common\src\importers\onepasswordImporters\onepassword1PuxImporter.ts: The actual export.data importer for parsing and importing vaults.
• \spec\common\importers\testData\onePassword1Pux\*.ts: Several files with test data using when executing the spec
• \spec\common\importers\onepassword1PuxImporter.spec.ts: Spec including several test cases to validate an import

Testing requirements

Test scenarios will be listed on the web PR.

Before you submit

• I have checked for linting errors (npm run lint) (required)
• I have added unit tests where it makes sense to do so (encouraged but not required)
• This change requires a documentation update (notify the documentation team)
• This change has particular deployment requirements (notify the DevOps team)