Hello, In the context of developping webapps for internal company purpose, I am looking to move away from .env files I just discovered infisical, and am wondering how app credentials that are passed from the app to infisical to allow retrieving the secrets are stored? Or did I just miss an important detail in the introductions? Regards,

Hi stephane. We have secret syncs which is a way that Infisical saves the secrets in the platforms where your application runs. For example: AWS, GCP, Vercel, Kubernetes and many more. If you already have secrets in those places, Infisical allows you to import them first so all your secrets are managed by Infisical.

Hi Matheus, I am not talking about the secrets my app requires, I am asking about the secret the app will provide to infisical to indentify itself, and get access to the secrets

For that we have Machine Identities.

I am missing something here. Let's say I use an APP token. I will create a project, roles, and secrets in infisical. My app will login to infisical using this token, to access the appropriate set of secrets. However this token, which should not live in the source code will be stored locally in an .env file or something similar? or am I still missing a point?

where are you hosting your application?

we host our apps on our own machines locally

in that case you would need to have the universal auth

clientId

and

secretId

in your env variables to be able to authenticate with Infisical. Most users actually host their apps in a cloud environment which we can authenticate automatically without any credentials. But in your case, I think you would need to keep the authentication credentials in your server.

ok, thank you