Moritz Johner

This is closely related to #975.

right! Thanks for scanning these old issues :bow: :broom:

Thats true, you can provide certs for authenticating with vault, what we can't do is use certs _just_ for mTLS and add a different auth method on top of it...

Hey @AnuragEkkati sure, go ahead! I'll assign this issue to you then :heart:. Do you want to add it to the store config? Or did you have something different in...

yeah, also i need to fixup the logo and devstats url on landscape.cncf.io, but that isn't a blocker. Thanks for the logos in the above linked PR, i can take...

It's a little to magical/implicit. I'd favor a separate field in the provider crd to make that explicit.

:thinking: I can't come up with a solution i like by changing the CRD (e.g. adding a `namespacedServiceAccountRef` that does what is described above). Although `defaults to the namespace of...

> regarding the floodgate that we want to put True, it shouldn't actually validate the credentials but use `utils.ValidateNetwork` instead. We must not forget that when implementing it across all...

> In the meantime, can we get a fix in 0.5.X to do what the documentation is saying yeah, i agree. We can get this into the next patch release...

TODOs to implement referent auth for other providers: - [x] HashiCorp Vault #1176 - [x] Kubernetes #1201 - [x] AWS Secrets Manager #1884 - [x] AWS Parameter Store #1884 -...