Releases: RedMageKnight/Flow.Launcher.Plugin.BitwardenSearch
Release list
v2.2.0 - EU Server Support
🌍 Major Feature: EU Server Support
This release adds official support for the Bitwarden EU server (vault.bitwarden.eu) while maintaining full backward compatibility.
✨ New Features
- 🇪🇺 EU Server Support: Choose between US (bitwarden.com) and EU (bitwarden.eu) servers
- 🎛️ Intuitive Server Selection: Easy dropdown in settings panel
- 🔄 Smart Server Switching: Automatic credential clearing when switching servers
- 📊 Clear Status Messages: Informative feedback during server configuration
🔧 Technical Improvements
- Enhanced server configuration management
- Improved error handling and logging
- Robust session management
- Performance optimizations
🛡️ Security Features
- Automatic credential clearing when switching servers
- Proper session cleanup during server changes
- Secure server validation
🎯 User Experience
- Zero breaking changes for existing users
- US server remains the default (backward compatible)
- Official server dropdown disabled when using custom servers
- Comprehensive status reporting
👏 Credits
Huge thanks to @KusayAhmad for this excellent implementation! The code quality, security considerations, and user experience design are outstanding.
🔗 Pull Request
- Resolves issue #22
- Implements PR #23 by @KusayAhmad
For European users: You can now seamlessly access your EU-based Bitwarden accounts through Flow Launcher!
For existing users: Nothing changes - your plugin will continue working exactly as before.
Contributors
Assets 3
v2.1.0
Introduced re-prompt for master password.
- Added feature to respect re-prompt for master password settings on individual vault items.
- Various bug fixes and minor feature improvements on the backend.
v2.0.0
Major Update Has Arrived!
Thank you everyone for your interest in using this plugin - your kind words and helpful suggestions have motivated me to develop this plugin far beyond what I originally intended when I first sought out to develop something for my individual use cases. I've learnt a lot more about what Flow Launcher can do by proxy of your suggestions and critique and have found myself wanting to use this much more thoroughly through these developments and additional features. It's also motivated me to look into developing new plugins or forking existing projects and trying to improve them.
With all that said, this is version 2.0.0 of the Bitwarden Search Flow Launcher plugin. Below are a list of the additional features:
- Self-Hosted instances are now supported!
- Before users found out that they could simply adjust their CLI configurations to adopt use of the plugin for their own instances.
- Now I've included parameters in the Flow Launcher settings pane for custom server attributes which will apply these server settings going forward with all of your subsequent requests.
- For those of you with more advanced setups, there are some addtional, optional server properties in an advanced dropdown. Otherwise, you can just provide the main URL of your self-hosted instance and be on your way.
- Vault item caching!
- Now the plugin will search a cached repository of your vault items that gets refereshed with every sync. Now instead of a sync just caching your respective icons, it will also write a cache of your vault items.
- No passwords are stored in the cache. The same information populated in the dropdown before when searching for items is essentially what's being stored here.
- Passwords and TOTP codes will still be queried for on demand using the CLI but searching for entries should be much faster now than it was before.
- Context menu support!
- When this was originally requested, I didn't even know Flow Launcher had context menus. I guess I should have tried since Raycast does but TIL.
- The same keyboard shortcuts still exist for those who got used to them, but now, if you want, you can use the context menu from within Flow Launcher instead when selecting a vault item.
- Seperate unlock window for obfuscating your master password!
- Some concerns arose regarding the original unlock method showing the master password in the Flow Launcher search bar when using the /unlock sub command.
- I've removed the /unlock sub command now (as well as all subcommands now) and opted for a separate window that utilizes a password-string text box so that the password is fully 'starred' out when entering it to unlock your vault.
- Some other little changes...
- Stopped the plugin from trying to login through the CLI immediately upon entering the client_id and instead waiting properly for the client_secret to be applied and saved.
- When switching between self-hosted and public servers (and vice versa), it now clears out the API credentials instead of trying to authenticate with them upon switch despite needing different ones and getting a bunch of authentication errors.
I can't really recall if there were any other little changes I made as I was focused largely on the top 4 and some of the changes I was intending on introducing in this version ended up going out in the hotfix I applied before this, so I took a bit of the thunder out.
In any case, I hope you all enjoy this update and let me know if you run into any issues. I tried to test this as thoroughly as I could with my own Vaultwarden instance and everything seemed to be kosher on my end, but who knows, everyone's got different setups and I could possibly be missing something.
v1.3.2
Authentication stop-gap fixes applied + others.
- Resolved issue with vault unlocking from plugin to newest version of CLI.
- Added the ability for new/existing users to download the latest version of the CLI automatically to a location of their choice and set the executable path and environment PATH variables accordingly.
- Added new notification option for auto-lock operation. Defaulted to disabled. When enabled, will notify user when vault is autolocked due to timeout if timeout settings are enabled.
I've been "graced" with some time to work on some of the additional requested features, so I'll be doing my best to work on these throughout the month.
v1.3.1
Fixed an unforseen issue with the autolock mech.
- Added a new autolock dropdown with options now instead of manual setting and modified the mechanism to actually work properly and log better.
v1.3.0
Big changes in this push! Version 1.3.0 introduces a couple of new features, provides several QoL changes, and a few optimization changes under the hood. Some of note include:
New features
- New CLI detection logic: download your bw.exe CLI file (please use the latest one), and go into your plugin settings to point to it and then, if it doesn't detect the location in your PATH, just click the text to have it do it for you!
- Added the ability to clear your clipboard automatically based on your preference.
- Added sync functionality - now you can sync your vault on demand which includes the process of updating your icons.
Fixes/Improvements
- Fixed a bug with the URI window not popping up after several changes.
- Fixed the icon querying and caching mechanisms. Now the query occurs after unlock and manual sync asychnrounosly (with the unlock process) and will no longer hang up the Flow Launcher UI causing incorrect selection references.
- Removed the /unlock command from appearing after your vault was already unlocked.
- Fixed issue with requiring a restart of the Flow Launcher plugin to commit api credentials.
- Fixed issue where I had to do funky workarounds to get the plugin to work without sending the api credentials by having the user sign in in advance of using the plugin so that a session key could be created and managed due to a bug in previous versions of the CLI not actually allowing you to properly sign in using the apikey parameter.
There's probably a few more I'm not thinking of, and maybe it's not as big of an update overall, but I've been working on this a while trying to get all the kinks out for the basic functionality and focusing hard on minimizing any actual interaction with the CLI by the user which I think I have effectively done now. In my testing, I did not once actually have to open up the command line/PowerShell which will hopefully be a big improvement in the user experience.
Hopefully this will make the experience much more seamless. Next updates I'll try to include configuration settings to use your own hosted bitwarden/vaultwarden server so that it will hopefully completely erase the need to use the terminal ever.
Thanks all for your patience 😊
v1.2.0
- Fixed settings panel client secret field from preventing manual typing of key by removing setting that applies on activity change.
- Now requires you to click the Save button next to client secret field to ensure changes are applied. Gives confirmation check on success.
- Fixed a bug that occurred when Flow Launcher was not shutdown cleanly and the Bitwarden CLI service did not properly shutdown.
- Included verbiage on plugin launch indicating if Bitwarden CLI is not installed that also links the user to the Download instructions page.
- If you install the Bitwarden CLI AFTER installing the plugin, you'll need to do a full close and re-open of Flow Launcher so that it can re-read your PATH variable.
- Minor code cleanup.
v1.1.0
- Modified client_secret management to use Windows Credential Manager now to handle storage of secret - is no longer being stored or referenced anywhere outside of that.
- Removed the old SecurePasswordHandler class as it no longer needs to be used for anything as there is no longer any need to convert strings back-and-forth to read in different calls to the CLI outside of the memory-controlled Windows Credential Manager mechanisms.
- Updated README to include detail about needing to restart Flow Launcher after setting up credentials in the plugin settings in order to get them to stick.
- Added a mask to the client_secret setting in the plugin settings so that the key, after being set, can no longer be referenced from the UI.