luxolus/open-vault
2
0
Fork 0
Code Issues 1 Pull requests Releases Activity

Fixing formatting

Browse source
This commit is contained in:
Chris Hoffman 2018-07-19 10:36:09 -04:00 committed by GitHub
parent 6a169ab00d
commit 712652c318
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
website/source/docs/auth/azure.html.md
View file

@ -27,8 +27,9 @@ The following documentation assumes that the method has been
* Client credentials (shared secret) for accessing the Azure Resource Manager with read access to compute endpoints. See [Azure AD Service to Service Client Credentials](https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-protocols-oauth-service-to-service) * Client credentials (shared secret) for accessing the Azure Resource Manager with read access to compute endpoints. See [Azure AD Service to Service Client Credentials](https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-protocols-oauth-service-to-service)
Required Azure API permissions to be granted to Vault user: Required Azure API permissions to be granted to Vault user:
* Microsoft.Compute/virtualMachines/*/read
* Microsoft.Compute/virtualMachineScaleSets/*/read * `Microsoft.Compute/virtualMachines/*/read`
* `Microsoft.Compute/virtualMachineScaleSets/*/read`
If Vault is hosted on Azure, Vault can use MSI to access Azure instead of a shared secret. MSI must be [enabled](https://docs.microsoft.com/en-us/azure/active-directory/managed-service-identity/qs-configure-portal-windows-vm) on the VMs hosting Vault. If Vault is hosted on Azure, Vault can use MSI to access Azure instead of a shared secret. MSI must be [enabled](https://docs.microsoft.com/en-us/azure/active-directory/managed-service-identity/qs-configure-portal-windows-vm) on the VMs hosting Vault.