I cannot delete one of the passwords screen . Are any solution for this ? . I newer seen this before . Today I moved the bw cli to /opt/local/bin/bw ,can this cause something like this ? Or I may misunderstand something ?
The folder is only a testing folder it does not exist , now I am not asked at every step as I set bw to Bitwarden environment ,or what it is called , but it takes 3 step in any way .
I think I got that 2 passwords screen because I tried to jump over the bw encode command - but not as I typed the full command out after that json output.
Yes I did ,but still I do not really understand why I need to go 3 steps before a folder is created.
bw get template folder | jq '.name="My First Folder"'
{
"name": "My First Folder"
}
After this ,it should go in to that long command an a folder is created ?
bw get template folder | jq '.name="My First Folder"' | bw encode | bw create folder
After this the folder should be created ? So I jumped over the second step ,and that is bw encode , but in the command above it is there bw encode ,this 2 step which created all those 2 passwords screen , as I believe ,. I do not know how this really works .
How long the BW_SESSION is active ? I mean in time ,say 1 hour or 2 hours ?.I newer used it as I am not often use the CLI - I set it up because of those passwords typing was really annoying.
But the 2 passwords screen appearing - I think that is because â bw encodeâ command I tried to jump over .
BW_SESSION is valid as long as you do not lock or logout (by running bw lock or bw logout, for example). If the server, for whatever reason logs you out, then it also will become invalid.
But there is no timeout for the CLI session to be active (like there is in other clients).
Running this:
bw get template folder | jq â.name=âMy First Folderââ | bw encode | bw create folder
Is like running these commands sequentially:
bw get template folder
jq â.name=âMy First Folderââ
bw encode
bw create folder
Commands number 1 and 4 require the CLI to be logged in and unlocked, command number 3 does not.
If a CLI command requires the CLI to be logged in and unlocked and you do not pass a valid BW_SESSION to it, then it will ask for your master password, every time.
Thatâs why you are prompted two times to enter your master password.
Btw, this is all explained in the help page I posted for you earlier. You should read it.
Yes it solved the problem ,it works wery well now . It was wery strange phenomenon after all ,but setting bw to session variable ,it solved the problem