Reputation: 1
I am using DefaultAzureCredential library to authenticate against azure to use key vault and my app is deployed in on prem. So right now I am using client id/secrete stored in environment variable of server. I don't want to store any kind of secret in environment variable. Is there any other approach by which I can access key vault in my on prem app without storing client id/secret in environment variable. If some one has access to server they can see that environment variable so I want to avoid that. I know if app is deployed in azure then I can enable managed identity but in my case it is on prem app and i registered that app in azure.
I dont want to store clientid/secret in environment variable. I would like to know any other approach by which this should get clientid.secret in memory and use that. I also dont want to store encrypted version of secret in environment variable
Upvotes: 0
Views: 67
Reputation: 16066
I think this section can help you to check if you can or can't do it.
I think using Powershell to Connect-AzAccount
a user in your on prem server can be an option, but this means your app are trying to access the Azure key vault on behalf of the user, so you also need to add the access policy for this user in Azure key vault page.
Upvotes: 0