Issues

[derritter88]

Hi there,

thanks for creating such smart shell command!!!

May I just suggest two things which comes up on my side?

1. Add the session ID

bash <(bw list items **--session xxxxxxx** | jq -r '.[] | select(.attachments != null) | . as $parent | .attachments[] | "bw get attachment \(.id) --itemid \($parent.id) --output \"./export/attachments/\($parent.id)/\(.fileName)\""')

2. Not sure what I am doing wrong but Bitwarden wants to know my password at every single attachment export - if there are one or two I do not care, but if there are a lot it's getting annoying.

[ckabalan]

Thanks for the big report. I'll look into this soon and make any appropriate adjustments! I suspect the password prompting may be previous bw commands caching my login or something. I'll figure that out and add it to the instructions or at least make a note.

[derritter88]

No problem - I am always happy to help with logging issues.

Not sure if you're into that but it might be also a smart idea to implement your script into a general bash script which does the login, saves the session ID into a variable, exports the "plain-text-only" json and finally run your script?!

[Alexander-Shukaev]

Yo, there appears to be a regression in Bitwarden CLI, at least that's how I understand it. Exported environment variable BW_SESSION is supposed to keep the vault unlocked in any subprocess. See bitwarden/cli#378, people seem to report that it worked for them, but it no longer works for me, password prompts upon export come regardless, while they don't upon sync.