daohualiuxiang
/
AspNetCore.Docs
mirror of https://github.com/dotnet/AspNetCore.Docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update Key Vault config provider samples (#4961)

pull/4986/head
Luke Latham 2017-12-12 10:20:36 -06:00 committed by Scott Addie
parent e46b2184a5
commit f9c17fbb49
4 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
aspnetcore/security/key-vault-configuration/samples/basic-sample/1.x/README.md
View File

@ -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"]`.

2
aspnetcore/security/key-vault-configuration/samples/basic-sample/2.x/README.md
View File

@ -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"]`.

2
aspnetcore/security/key-vault-configuration/samples/key-name-prefix-sample/1.x/README.md
View File

@ -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`.

2
aspnetcore/security/key-vault-configuration/samples/key-name-prefix-sample/2.x/README.md
View File

@ -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`.