azure-keyvault

问题 I have an object value in the key vault key of azure and trying to read the value at the startup class but the value is always null. Program.cs var azureServiceTokenProvider = new AzureServiceTokenProvider(); var keyVaultClient = new KeyVaultClient( new KeyVaultClient.AuthenticationCallback( azureServiceTokenProvider.KeyVaultTokenCallback)); config.AddAzureKeyVault( vaultConfig.AzureVaultUrl, keyVaultClient, new DefaultKeyVaultSecretManager()); Startup.cs public virtual void ConfigureSettings

问题 I am finding Application Registrations in Azure very confusing. In my question here AuthClientId and Application Id turned out to be the same thing, so why are two names being used? What is the logic behind this choice of naming? [Update] From Joy's link to the glossary I see application id (client id) "The unique identifier Azure AD issues to an application registration that identifies a specific application and the associated configurations. This application id (client id) is used when

问题 I am finding Application Registrations in Azure very confusing. In my question here AuthClientId and Application Id turned out to be the same thing, so why are two names being used? What is the logic behind this choice of naming? [Update] From Joy's link to the glossary I see application id (client id) "The unique identifier Azure AD issues to an application registration that identifies a specific application and the associated configurations. This application id (client id) is used when

问题 I am seeking some clarity on the best way to integrate Key Vault in ARM deployments within Azure DevOps. For example, deploying an App Service and creating a Managed Service Identity so that it can get secrets from the key vault for a pre-existing Database. 1) In the Azure portal, I have manually created a new Service Principal for the App service with "Get" and "List" permissions in the access policy. 2) In My DevOps Project under the project settings I have created a service connection. 3)

问题 I am seeking some clarity on the best way to integrate Key Vault in ARM deployments within Azure DevOps. For example, deploying an App Service and creating a Managed Service Identity so that it can get secrets from the key vault for a pre-existing Database. 1) In the Azure portal, I have manually created a new Service Principal for the App service with "Get" and "List" permissions in the access policy. 2) In My DevOps Project under the project settings I have created a service connection. 3)

问题 I was trying to Create a Application in Azure AD with Azure PowerShell Certificate authentication, below is the Powershell snippet: Login-AzureRmAccount $cert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate("PATH_TO_CER_FILE") $key = [System.Convert]::ToBase64String($cert.GetRawCertData()) $app = New-AzureRmADApplication -DisplayName "SetupTet4" -HomePage "http://localhost" -IdentifierUris "http://localhost" -KeyValue $key -KeyType AsymmetricX509Cert New

问题 I was trying to Create a Application in Azure AD with Azure PowerShell Certificate authentication, below is the Powershell snippet: Login-AzureRmAccount $cert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate("PATH_TO_CER_FILE") $key = [System.Convert]::ToBase64String($cert.GetRawCertData()) $app = New-AzureRmADApplication -DisplayName "SetupTet4" -HomePage "http://localhost" -IdentifierUris "http://localhost" -KeyValue $key -KeyType AsymmetricX509Cert New

问题 I'm trying to get secret from azure key vault. So i found the code below but got an error. AppServiceMSICredentials credentials = new AppServiceMSICredentials(AzureEnvironment.AZURE); KeyVaultClient keyVaultClient = new KeyVaultClient(credentials); String secret = keyVaultClient.getSecret("uri", "secretName").value(); I got an error like this: Error >>> endpoint == null I also tried this way: AppServiceMSICredentials credentials = new AppServiceMSICredentials(AzureEnvironment.AZURE, "MSI Url?

问题 I have WebApp which I host on Azure App Service. It also uses certain values from KeyVault. WebApp authenticates to KeyVault using Managed Service Identity of AppService and assigning the identity permissions in keyvault it works. However, I am yet to figure out, how can I possibly get around this or perform dummy authentication when I am debugging on localhost. because localhost can't directly authenticate to keyvault. Any ideas would be great. 回答1: If we want to debug on the localhost, we

问题 I have a template to create a key vault and a secret within it. I also have a service fabric template, that requires 3 things from the key vault: the Vault URI, the certificate URL, and the certificate thumbprint. If I create the key vault and secret with powershell, it is easy to manually copy these 3 things from the output, and paste them into the parameters of the service fabric template. However, what I am hoping to do, due to the fact that this cert has the same life cycle as the service