Dear Keeper Commander Team,

I have the following purpose for the use of the CLI:

For logging into a certain customer environment, we are using a shellscript, in which we are opening an interactive CLI application. This application is sequentially asking for the login, which we need to type in and press RETURN, then the password, again confirmed by RETURN and finally the TOTP follwed by RETURN.

All the needed information is stored in my Keeper Vault.

I wanted to use the Commander CLI to access these information and provide them to the other CLI application for faster and more convenient login.

I am not the Keeper Administrator of my organisation. I tried to enable persistent-login, but this is disabled by our Admin. Here are some information about my account:

As you can see, I can successfully use the Keeper CLI to login via SSO. And from there I can access the fields of the entry:

And of course login-status returns that I am logged in:

But from within the Commander CLI, I can not process the outputs further.

In Gitbash, I can run keeper-commander login email@address.tld and I can successfully use SSO login:

Running keeper-commander login-status does not return anything though:

I do have the ~/.keeper files:

My assumption is that because of this, whenever I run any of the commands, I am asked to login again:

As I need 3 fields out of Keeper Vault, I would need to login 3 times, which destroys the purpose of automation.

So my questions:

1. Is there the possibility to login once and receive several fields returned? Currently clipboard-copy does not support a list for --field.
2. The keeper-commander get command does support export in a json format. But I can not grep this because of the prior stdout of the SSO login.
3. The same goes for the keeper-commander cc command. I could not find a way to further process the output, because of the SSO login output to the console. Is there a way around that?

Thank you for looking into this.