jzadra

THIS WORKFLOW IS DEFUNCT. AN UPDATED FORK IS AVAILABLE. For anyone else who stumbles up on this thread trying to get this workflow to work, don't bother. It is defunct and not maintained. A different author forked it and it works out of the box with Alfred 4: http://www.packal.org/workflow/lastpass-search

I've just installed this workflow, but any of the initial set up commands to set my email, set timeout, and login do not produce any response (neither an error nor a confirmation). When I then try to retrieve a password, it says I'm not logged in. I have lastpass-cli version 1.3.3_1, Alfred 4.6.5, and installed Capture::Tiny using 'lib::local'. I'm on Monterey 12.3.1. I previously had lastpass-cli installed and working in iTerm. In case the issue was the install arguments suggested in the setup guide for the workflow, I uninstalled it and tried installing with the arguements, but I was unable to install lastpass cli with the arguments `--with-pinentry --with-doc`, as both generated errors: Error: invalid option: --with-pinentry Error: invalid option: --with-doc I've also tried logging in using the terminal (successfully) and then using the workflow, but it still reports not logged in.

Thanks. I was curious about lines 14 and 15 in the google-drive.rb file that have static client info set. Who's ID is that? CLIENT_ID = '978117856621-tvpnqtr02b8u0bgnh75sqb1loq1f5527.apps.googleusercontent.com' CLIENT_SECRET = 'rty2NIATZfWFWSDX-XPs2usX'

When logging in, it wants to give access to all my files to "Alfred Drive Workflow". Does this open my drive security to a 3rd party? I see that a CLIENT_ID and CLIENT_SECRET is predifined in the python script. Is there any documentation on who gains access and security in general using this workflow?