Test importing codes from a password manager

Use a test account to check whether the KeySigner macOS authenticator can copy a time-based sign-in code from a 1Password 1PUX, KeePass XML or compatible KeePassXC XML export.

Before you start

KeySigner macOS build with password-manager import enabled

  • Use a local 1Password 8 1PUX export no larger than 16 MiB from a test vault.
  • Use a local KeePass 2 XML export no larger than 16 MiB from a test database.
  • Use a local KeePassXC 2.8.0 command-line XML export no larger than 16 MiB and choose KeePass XML in KeySigner.
  • Check the KeePassXC version

Data and access

Shared or checked
KeySigner copies supported time-based code fields from the test export. The app you sign in to receives a generated code.
Check separately
The source copy can still generate codes. The importer leaves passwords, passkeys and attachments in the source manager.
  1. Prepare a test code

    In 1Password 8, KeePass 2 or KeePassXC 2.8, save a time-based one-time password (TOTP) for a test account you control. Pick an account you can still access if the import fails.

    Check. The source shows a current code for the chosen issuer and test account. The independent recovery option is available.

  2. Export the test data

    Export the test account or database to a private folder on your computer, outside any synced folder. The export can contain unencrypted passwords and codes.

    Choose your export instructions

    1Password 8 on Mac
    Open File → Export, select your test account, then choose 1PUX.
    1Password 8 on Windows or Linux
    Open the three-dot menu at the top of the sidebar, select Export and your test account, then choose 1PUX.
    KeePass 2
    Open File → Export and choose KeePass XML (2.x).
    KeePassXC 2.8.0
    Use the command-line XML export with an ordinary time-based code.

    Check. The temporary export exists in the private, unsynced location and uses the format you selected.

  3. Review and import one code

    In KeySigner for Mac, open Accounts, choose Add (+), then Sign-in codes and backup. Unlock and choose Import from a password manager. Choose 1Password 1PUX or KeePass XML. Use KeePass XML for a KeePassXC export too. Select your file, review the test item, then choose Import this code.

    Check. The review shows the expected test account. After import, the account appears in KeySigner’s sign-in code list.

  4. Check the copy and clean up

    Use the new KeySigner code on the test service while keeping the original code available. When the test is finished, remove the temporary export. Keep the source account until you have verified access.

    Check. The service accepts a fresh KeySigner code and the original copy remains available. Remove the temporary export from the test computer.

Check your result

The test service accepts a KeySigner code for the same account. KeySigner copies supported code fields and leaves the source copy available. Passwords, passkeys and attachments stay with the source password manager.

How to verify your setup

If you get stuck

The import option or test item is unavailable

Check that you’re using a KeySigner macOS build with Sign-in codes and backup available. Unlock the authenticator, check that the export is a local file no larger than 16 MiB, and confirm the source item has a time-based code. Use 1PUX or XML. For KeePassXC, Steam codes and older code field formats are outside this flow.

KeySigner messages for this setup

Report a problem with this guide

Explore all setup guides →