Keepassx Windows

[Lakia Throssell]

TechSavy 1 Password user here, running a family account. The setup in question is with the 1Password desktop App on Win10.

I have a desktop application that spawns a login screen, which I want to use 1Password to fill.

The login screen does not allow copy and paste of credentials, only manual type - so using 1Password's "click and drag" functions or simple Copy/Paste via Quick Access don't work. It's not in a web browser so browser autofill is also off the table.

I can't find any way to get 1Password to auto-fill to this application.

And yet - downloading a portable version of open-source KeePass has me up and running in on this in about 10 mins. Keepass, free and open source, allows me to target the window and autofill from its own DB.

Keepass works perfectly here, despite being open source and free. Why can't 1Password, which we pay a premium for, do this as well ? The code is literally freely available (depending on whatever KeePass's license is of course). Am I missing the functionality in 1Password somewhere ? Or is there some reason this wasn't implemented ?

@K2342 you mentioned "click and drag" - actually, if you open some item in the 1Password desktop app, and drag some field from 1Password to the userid or password input field of the app you want to login, the data is autofilled. From Windows' point of view, the data is simulated keyboard input with this, not copy+paste, so it should work even if your app doesn't support pasting. Did you actually try this drag+drop operation?

Another suggestion I'd like to offer is the Type in window functionality from 1Password 8 for Windows. Could you try right-clicking the username and password fields in 1Password > Type in window > [destination window], and let us know if this works better for you or not at all?

With regard to drag and drop losing characters, we do have an issue opened with the team. Could you let us know what desktop application you are having troubles with so I can pass these details along to the team?

Finally, regarding to the Windows equivalent Universal Autofill for Mac, this is on the Product team's roadmap, but I have no further news to share. Keep an eye on 1Password Releases for the latest updates and new features added to 1Password 8. Thanks!

"Type in Window" is nifty. I hadnt noticed that before (and must have missed it in the documentation? :-) ) - and it shows me that 1Password has already some of the functions needed for a Keepass-like Global Auto-fill on Windows. Being able to identify the windows available is big.

But I see an issue there too. It actually doesnt work for me in this workflow. The list of windows available doesnt appear to have a close match to the window I want - it seems like it's having trouble identifying the window at all - and so nothing happens when I try it.

My usecase is somewhat complex here. This login form is spawned by Brave Browser -> Citrix Workspace -> VMWare Horizon Client. So a few layers in. 1Password seems only able to recognize it as "Citrix Workspace" and no further.

It is complex, but again free and open source Keepass handled it without issue and more completely (it autofills all fields and submits, while minimized, with a keyboard shortcut! ) - so it's certainly doable. I currently use Keepass to do this a couple times a day because the time and energy it saves really adds up when Im bouncing around different VMs.

It's good to hear a 1Password Universal Autofill for Windows is in the works.

"Type in Window" is a neat feature, and I like it more than the "Click and drag" - but it's also just a shadow of a real Universal Autofill. I dont quite understand why development resources are being spent on those essentially workarounds, instead of just funneling everything to a true Windows Universal Autofill (like Keepass for Windows has, and 1Password for Mac has). 1Password Windows Autofill to me would render "Type In Window" and "Click and Drag" obsolete and would help increase feature parity on your platforms (always a good goal in its own right).

Thanks for getting back to us with the details about your use case and giving type in window a try. VMWare is the issue here with type in window. I've had some recent conversations with our development team. We're currently tracking and looking into more cases of customers who are interested in this capability. I've included your details there for the team.

@ag_mike_d - Sure thing.

Yep, VMWare is often the issue ha, but again - Keepass does it and has shared their solution with the world - so the technical specs are out there. They just need ported into 1Password's framework.

Hello @ag_mike_d,

I have the same problem with VMware Horizon Client in multiple layers like @K2342. Is there an update to the current development?

I recently switched from KeePass to 1Password and now I have to type my very safe passwords (length and complexity) by hand :(

I would appreciate a solution to this issue very much.

Hello @ag_mike_d - Looking forward and excited to seeing this Universal Autofill option added for Windows as well. Do you happen to have any updates on when this may be added? I tried the type in window command but that seems to only be browser specific and I'm not seeing the option within the quick access menu, only the full 1password desktop app. Thanks for any insight even if it's something you can comment on yet. Will be really nice to be able to use this as a gamer that has multiple games require a log-in that currently requires a bunch of keyboard shortcuts from quick access to get the username and password input within the launcher.

Hi @Electronic, thanks for reaching out! We don't have any news to share about this at the moment, however you can keep an eye on our release notes to stay up to date with any changes: 1Password Releases - Windows

In earlier versions of Ubuntu and KeePass I used to run KeePass with wine, but in the latest versions, the YubiKey is not detected in the wineenvironment ("error connecting to yubikey"). No problem, I thought: Let's use keepassx. Seems not that easy, though...

I followed this comprehensive manual to install KeePassX with challenge response 2-factor support for linux (ubuntu/lubuntu). The repository ppa:hda-me/keepassx2-yubico for eoan is not yet available, but using bionic instead seems to work quite fine. At least on the first glance.

Update: When running keepassx from the console, the "challenge response" option is available. But not, when running KeePassX from the start menu. The correct combination of password and key response still results in "wrong key or file damaged". With the windows KeePass, the file can still be opened.

In my experience K2A also has the ability to copy either the user name or password to the clipboard from the notification shade. You look up the site/account you need to sign in to and the notification shade will automatically have the two options available to you.

PIN unlock is also secure as it is used in a form of 2FA. In order to unlock the database, you must have access to your Google Drive for some app-private data, and the PIN. Neither one individually can unlock your passwords.

I have been running LastPass the past three months on three different devices (two Androids) using the same account and minimal issues. Having easy access to all my passwords on all of them is why I got LastPass. I used KeePass for many years and it served me well but I needed to access passwords from my smartphone. It may not be the most secure approach and it is a bit unsettling to trust the cloud with my valuable information, but simplicity of the solution won out. Happy so far.

Moreover, whereas keepass appears to offer near exact same 256 AES encryption, not certain that it offers full cloud synchronisation too enabling all cross platform devices like PC, Mac, tablet (android or iOS) & phone to be restored from encrypted cloud database if the device(s) themselves are lost or stolen. Just depending on a local copy of the encrypted database only for example can be risky. SafeInCloud also seems to have similar portable tools. No not open source but just a one off (very inexpensive) support payment instead.

If someone steals my tablet and gains full access before I realize my loss,

I will not worry.

There is no tablet access to my bank etc.

My tablet does NOT have passwords etc. to my Desktop email accounts.

I went through this exercise when I bought my first Android phone 18 months ago. In the end I chose to store my password database on OneDrive and use it via Keepass2Android on my phone. This has worked brilliantly.

However, the main password manager on my PC, which is used for all my passwords and is the master, is separate (a different program entirely). The cloud db is restricted to a small subset (common, non-financial passwords), only 10% or so of the total in the master db.

There is no way to do this automatically, but you can do it in a couple of ways.

1. Move the portable entries into a new database and sync that database. KeePass allows you to open several databases at once, automatically with the KeeAutoExec plug-in.

2. Move the portable entries into a new folder in your database and export them to a new database. The downside is there is no sync for the exported entries.

I have had great luck with Dashlane. On my android phone and windows laptop and desktop. All work well, not synced since I did not buy premium service. You can export/import from/to different devices.

That is not the case, sync is whole of database only.

To use a subset database you need to move the subset to another database and use that database to sync with the cloud / other subset database.

To open more than one database in KeePass use the KeeAutoExec plug-in and associated triggers from the trigger example page.

There is a possibility of data loss doing it that way. Consider this scenario:

1. You both change something in KeePass but the DB sync fails on the machine that made the change first.

2. The DB sync re-starts and finds a newer file which it downloads.

3. The first KeePass change is now lost in the sync.

You can recover the change by going back to the DB conflicted copies, but that is a manual process.

The link in post #37 shows you how to avoid that clash.

3a8082e126