From f9c17fbb49851ac90f3788e592440e1fb448769a Mon Sep 17 00:00:00 2001 From: Luke Latham <1622880+guardrex@users.noreply.github.com> Date: Tue, 12 Dec 2017 10:20:36 -0600 Subject: [PATCH] Update Key Vault config provider samples (#4961) --- .../key-vault-configuration/samples/basic-sample/1.x/README.md | 2 +- .../key-vault-configuration/samples/basic-sample/2.x/README.md | 2 +- .../samples/key-name-prefix-sample/1.x/README.md | 2 +- .../samples/key-name-prefix-sample/2.x/README.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/aspnetcore/security/key-vault-configuration/samples/basic-sample/1.x/README.md b/aspnetcore/security/key-vault-configuration/samples/basic-sample/1.x/README.md index ffd18897d8..99fc035fa6 100644 --- a/aspnetcore/security/key-vault-configuration/samples/basic-sample/1.x/README.md +++ b/aspnetcore/security/key-vault-configuration/samples/basic-sample/1.x/README.md @@ -16,7 +16,7 @@ For more information on how the sample works, see the [Azure Key Vault configura * `SecretName`: `secret_value_1` * `Section--SecretName`: `secret_value_2` * Register the sample app with Azure Active Directory. - * Authorize the app to access the key vault. When you use the `Set-AzureRmKeyVaultAccessPolicy` PowerShell cmdlet to authorize the app to access the key vault, provide `List` and `Get` access to secrets with `-PermissionsToKeys list,get`. + * Authorize the app to access the key vault. When you use the `Set-AzureRmKeyVaultAccessPolicy` PowerShell cmdlet to authorize the app to access the key vault, provide `List` and `Get` access to secrets with `-PermissionsToSecrets list,get`. 2. Update the app's *appsettings.json* file with the values of `Vault`, `ClientId`, and `ClientSecret`. 3. Run the sample app, which obtains its configuration values from `IConfigurationRoot` with the same name as the secret name. * Non-hierarchical values: The value for `SecretName` is obtained with `config["SecretName"]`. diff --git a/aspnetcore/security/key-vault-configuration/samples/basic-sample/2.x/README.md b/aspnetcore/security/key-vault-configuration/samples/basic-sample/2.x/README.md index 3c4f3122ce..6e32ee4de8 100644 --- a/aspnetcore/security/key-vault-configuration/samples/basic-sample/2.x/README.md +++ b/aspnetcore/security/key-vault-configuration/samples/basic-sample/2.x/README.md @@ -13,7 +13,7 @@ For more information on how the sample works, see the [Azure Key Vault configura * `SecretName`: `secret_value_1` * `Section--SecretName`: `secret_value_2` * Register the sample app with Azure Active Directory. - * Authorize the app to access the key vault. When you use the `Set-AzureRmKeyVaultAccessPolicy` PowerShell cmdlet to authorize the app to access the key vault, provide `List` and `Get` access to secrets with `-PermissionsToKeys list,get`. + * Authorize the app to access the key vault. When you use the `Set-AzureRmKeyVaultAccessPolicy` PowerShell cmdlet to authorize the app to access the key vault, provide `List` and `Get` access to secrets with `-PermissionsToSecrets list,get`. 2. Update the app's *appsettings.json* file with the values of `Vault`, `ClientId`, and `ClientSecret`. 3. Run the sample app, which obtains its configuration values from `IConfigurationRoot` with the same name as the secret name. * Non-hierarchical values: The value for `SecretName` is obtained with `config["SecretName"]`. diff --git a/aspnetcore/security/key-vault-configuration/samples/key-name-prefix-sample/1.x/README.md b/aspnetcore/security/key-vault-configuration/samples/key-name-prefix-sample/1.x/README.md index c55fcb47d4..da19f13ff8 100644 --- a/aspnetcore/security/key-vault-configuration/samples/key-name-prefix-sample/1.x/README.md +++ b/aspnetcore/security/key-vault-configuration/samples/key-name-prefix-sample/1.x/README.md @@ -15,7 +15,7 @@ For more information on how the sample works, see the [Azure Key Vault configura * `5000-AppSecret`: `5.0.0.0_secret_value` * `5100-AppSecret`: `5.1.0.0_secret_value` * Register the sample app with Azure Active Directory. - * Authorize the app to access the key vault. When you use the `Set-AzureRmKeyVaultAccessPolicy` PowerShell cmdlet to authorize the app to access the key vault, provide `List` and `Get` access to secrets with `-PermissionsToKeys list,get`. + * Authorize the app to access the key vault. When you use the `Set-AzureRmKeyVaultAccessPolicy` PowerShell cmdlet to authorize the app to access the key vault, provide `List` and `Get` access to secrets with `-PermissionsToSecrets list,get`. 2. Update the app's *appsettings.json* file with the values of `Vault`, `ClientId`, and `ClientSecret`. 3. Run the sample app, which obtains its configuration values from `IConfigurationRoot` with the same name as the prefixed secret name. In this sample, the prefix is the app's version, which you provided to the `PrefixKeyVaultSecretManager` when you added the Azure Key Vault configuration provider. The value for `AppSecret` is obtained with `config["AppSecret"]`. 4. Change the version of the app assembly in the project file from `5.0.0.0` to `5.1.0.0` and run the app again. This time, the secret value returned is `5.1.0.0_secret_value`. diff --git a/aspnetcore/security/key-vault-configuration/samples/key-name-prefix-sample/2.x/README.md b/aspnetcore/security/key-vault-configuration/samples/key-name-prefix-sample/2.x/README.md index 227f1411eb..ff07bf0642 100644 --- a/aspnetcore/security/key-vault-configuration/samples/key-name-prefix-sample/2.x/README.md +++ b/aspnetcore/security/key-vault-configuration/samples/key-name-prefix-sample/2.x/README.md @@ -12,7 +12,7 @@ For more information on how the sample works, see the [Azure Key Vault configura * `5000-AppSecret`: `5.0.0.0_secret_value` * `5100-AppSecret`: `5.1.0.0_secret_value` * Register the sample app with Azure Active Directory. - * Authorize the app to access the key vault. When you use the `Set-AzureRmKeyVaultAccessPolicy` PowerShell cmdlet to authorize the app to access the key vault, provide `List` and `Get` access to secrets with `-PermissionsToKeys list,get`. + * Authorize the app to access the key vault. When you use the `Set-AzureRmKeyVaultAccessPolicy` PowerShell cmdlet to authorize the app to access the key vault, provide `List` and `Get` access to secrets with `-PermissionsToSecrets list,get`. 2. Update the app's *appsettings.json* file with the values of `Vault`, `ClientId`, and `ClientSecret`. 3. Run the sample app, which obtains its configuration values from `IConfigurationRoot` with the same name as the prefixed secret name. In this sample, the prefix is the app's version, which you provided to the `PrefixKeyVaultSecretManager` when you added the Azure Key Vault configuration provider. The value for `AppSecret` is obtained with `config["AppSecret"]`. 4. Change the version of the app assembly in the project file from `5.0.0.0` to `5.1.0.0` and run the app again. This time, the secret value returned is `5.1.0.0_secret_value`.