Jump to content

blacs30

Member
  • Content Count

    18
  • Joined

  • Last visited

  • Days Won

    1

blacs30 last won the day on August 22 2019

blacs30 had the most liked content!

About blacs30

  • Rank
    Newbie

Profile Information

  • Location
    Germany

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. If Alfred is allowed to send notifications you should set a confirmation notification like this (screenshot 1) You can also double check the keychain if items have been created there. Open the app "Keychain Access", search for "bitwarden", you should be able to see couple of entries, but at least the one for the email-address. Can you try to search for an item like "bw google", it could be that you also need to run "bwunlock", that is needed in case bitwarden cli unlock is run in the meantime. It is so that bitwarden then invalidates the previous generated session key. Thanks @deanishe taking part here as well, it's an honour I hope to soon fully rewrite this workflow in go with help of your library.
  2. Also sorry to you @thomasSDK for my very very last reply. I will configure my notifications here on the forum. This error you showed looks heavily like this one https://stackoverflow.com/questions/53603246/strange-error-running-osascript-e-command-on-macos-mojave
  3. I'm sorry not to have answered before @Al30 . I think I messed up my notifications here from the forum. Do you still need help? For the logs it looked like that the setting for 2fa mode might have been wrong. I would ask you to try to login via cli in the terminal. If the cli asks you to choose an 2fa auth method (which only happens if multiple 2fa ways are setup) then you need to configure the method otherwise it's 0.
  4. @alexbet just for confirmation, are you using version 1.2.4? You can also find it here on Github https://github.com/blacs30/bitwarden-alfred-workflow/releases
  5. Hi @alexbet, thanks for the information. That is a strange behaviour. Can you please check the logs of the workflow (in the Alfred Preferences select the workflow and then enable the debug mode by clicking on the bug icon at the top right )
  6. @alexbet Thanks for reporting this issue. So the workflow doesn't ask you for the password for your bitwarden account, correct? Which macOS version do you run? Are you running Alfred 4 and have you upgraded it from version 3 or is it der first time you are using Alfred? Did you allow Alfred in the Accessibility settings (System Preferences > Security & Privacy > Privacy > Accessibility > add Alfred here) Currently there is a known issue for a clean Alfred 4 installation on macOS without having Alfred 3 installed before that. I didn't find time to fix it yet.
  7. The workflow requires the Bitwarden CLI to be installed. You can find binaries here: https://github.com/bitwarden/cli/releases or you can use Homebrew to install it
  8. Which version is your bitwarden cli? With the latest version 1.7.4 it is still running.
  9. @andresm1126 I understand, I have it the same way. The bitwarden alfred workflow will ask you for the 2fa code (6 digits) - but for this you need to use the command `bwset2fa on` in Alfred. That will tell the workflow when you login via alfred to ask 1. for the password and then 2. for the 6 digit 2fa code. Screenshot attached, hope that helps.
  10. Hi @andresm1126 for 2fa please enable 2fa in the Alfred workflow with `bwset2fa on` In case you were already logged in in Alfred (which I think is not the case for you) logout first `bwlogout` and then login again with `bwlogin`
  11. Thanks @deanishe for pointing out this. There might be probably more odd in the code: https://github.com/blacs30/bitwarden-alfred-workflow/tree/master/workflow-main-scripts Feel free to either create an issue or pull request if you want. I am happy to be able to learn more as I am still quite unexperienced in Python.
  12. Glad it’s of help. Feel free to report issues here or on github for things you notice.
  13. Hi @springles, thanks for reporting this issue and fixing it. Version 1.2.2 supports spaces in passwords now. I've used shlex.split() and double quotes around the password. https://github.com/blacs30/bitwarden-alfred-workflow/releases/tag/1.2.2 def login(login_mail, mfa_enabled=None, mfa_method=None): [...] if not mfa_enabled: cmd = "/usr/local/bin/bw --raw login \"{login_mail}\" \"{password}\"".format(login_mail=login_mail.strip(), password=password.strip()) elif mfa_enabled and not mfa_method: mfa_code, err, status, message = build_osascript(login_mail, 'Enter Bitwarden second factor code', True) cmd = "/usr/local/bin/bw --raw login \"{login_mail}\" \"{password}\" --code {mfa_code}".format(login_mail=login_mail.strip(), password=password.strip(), mfa_code=mfa_code.strip()) else: mfa_code, err, status, message = build_osascript(login_mail, 'Enter Bitwarden second factor code', True) cmd = "/usr/local/bin/bw --raw login \"{login_mail}\" \"{password}\" --method {mfa_method} --code {mfa_code}".format(login_mail=login_mail.strip(), password=password.strip(), mfa_method=mfa_method.strip(), mfa_code=mfa_code.strip()) split_cmd = shlex.split(cmd) proc = Popen(split_cmd, env=my_env, stdout=PIPE, stderr=PIPE)
  14. Hi Andrey, oh, I am sorry. It could be now some issue with keychain. Can you please do the following: Check in the keychain if a session-key entry exist. And could you please also enable debug (the bug in the top right corner) in Alfred and post the result, shouldn't contain complete secrets. Thanks a lot. Edit: Please see version 1.2.1. I hope this fixes your issue. Thanks for your patience.
  15. Hi Andrey, I've just released version 1.2.0 which hopefully fixes that issue of yours. Can you please try that version and let me know if it works now? https://github.com/blacs30/bitwarden-alfred-workflow/releases/tag/1.2.0 Thanks!
×
×
  • Create New...