Encrypted-at-Rest Password or Token Storage

[sbernheim]

Proposed Feature

Store an encrypted authentication token or password so that the user need not type their password each time they run kconnect to reconnect to a cluster.

The kconnect CLI could store a private keyfile in the ~/.kconnect directory or support a configuration that refers to a Private key in a separate location (such as ~/.ssh/id_rsa) either for direct authentication to the IDP or to encrypt a token or password stored in ~/.kconnect/config.yaml or a separate credentials file.

Problem

It's annoying to have to type your password each time you reconnect to the cluster, especially when you are authenticating via an Enterprise SSO solution. The tool should support storing a longer-lived token for SSO or a password in an encrypted format for each IDP.

[richardcase]

I think is a really good idea. We can also support passing via stdin.