Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I use Bitwarden instead of 1Password, and wanted to get it working with FFXIVQuickLauncher. Bitwarden's CLI unfortunately does not have integration with the Desktop install, like 1Password does so you either have to store the password somewhere, or enter it each time the script is executed.
These scripts were based on the 1Password implementation, allowing both a manual or automatic login. Optionally, the user can store their Bitwarden master password in an encrypted blob on disk. This encrypted blob can only be decrypted on the system it was originally encrypted on (using PowerShell SecureString & DPAPI). This helps to mitigate if the user's system were compromised, an attacker could not read a plain-text master password, compromising the entire vault. However, there are still security implications to consider with this setup. It's much better than a plain-text password, or a plain-text OTP seed though.