I've just been playing with the KeyPassXC integration and it works nicely. One issue I noticed was that XPipe gives a bit of an error when the KeyPass vault is locked and needs the user to unlock it to retrieve the password. I was thinking this would be a bit bothersome if the user has a KP vault that locks frequently.
When I use the KeyPassXC_browser extension, when the KP vault is locked, it allows you to popup the KP application to unlock it, the extension then does a recheck and retrieves the password.
I was wondering if it might be possible to do something similar in the XPipe system. My thoughts were:
- Query the KeyPass database, this returns the "Database is closed" error.
- The XPipe system displays an option to "open KeyPassXC to unlock" (or cancel). I'm not familiar with other KeyPass implementations, but it may be possible to either specify the KeyPass UI or present a list of installed options?
- Once the user clicks on the "open KeyPass" button, XPipe displays a little "waiting" or "retrying" logic, but also:
- Runs the KeyPassXC application, this should bring the application to the front.
- User unlocks their KP vault.
- XPipe is checking the vault status and brings itself to the front here where it continues the connection.
I've just been playing with the KeyPassXC integration and it works nicely. One issue I noticed was that XPipe gives a bit of an error when the KeyPass vault is locked and needs the user to unlock it to retrieve the password. I was thinking this would be a bit bothersome if the user has a KP vault that locks frequently.
When I use the KeyPassXC_browser extension, when the KP vault is locked, it allows you to popup the KP application to unlock it, the extension then does a recheck and retrieves the password.
I was wondering if it might be possible to do something similar in the XPipe system. My thoughts were: