In an ideal world we would like to be passwordless 100%. And we can already do that with SAML/OIDC apps, SSH, etc. For these flows passwords do not exist.
However, the companies we work with always have some legacy app that just does not support modern identity protocols. For that we have to fill passwords and provide vaulting capabilities to offer end to end experience. The reason we decided to add vault is to make things simple and integrated, so that company does not need to manage separate product. Agreed, 1P and some others are known-and-trusted, but we hope to earn this trust over time. And using our Vault is optional.
Right now we are planning to release RDP support for Windows servers, and then we were planning to focus on adding support for databases. That is why your feedback is critical as we can reassess the priorities regarding Kubernetes.
In an ideal world we would like to be passwordless 100%. And we can already do that with SAML/OIDC apps, SSH, etc. For these flows passwords do not exist.
However, the companies we work with always have some legacy app that just does not support modern identity protocols. For that we have to fill passwords and provide vaulting capabilities to offer end to end experience. The reason we decided to add vault is to make things simple and integrated, so that company does not need to manage separate product. Agreed, 1P and some others are known-and-trusted, but we hope to earn this trust over time. And using our Vault is optional.
Right now we are planning to release RDP support for Windows servers, and then we were planning to focus on adding support for databases. That is why your feedback is critical as we can reassess the priorities regarding Kubernetes.