You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sdk/keyvault/Azure.Security.KeyVault.Administration/README.md
+12-13Lines changed: 12 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ cryptographic keys for your cloud applications using FIPS 140-2 Level 3 validate
5
5
6
6
The Azure Key Vault administration library clients support administrative tasks such as full backup / restore and key-level role-based access control (RBAC).
@@ -24,7 +24,7 @@ See the final two steps in the next section for details on creating the Key Vaul
24
24
25
25
### Authenticate the client
26
26
In order to control permissions to the Key Vault service, you'll need to create an instance of the [KeyVaultAccessControlClient][rbac_client] class.
27
-
You need a **vault URL**, which you may see as "DNS Name" in the portal, and **client secret credentials (client id, client secret, tenant id)**
27
+
You need a **Managed HSM URL**, which you may see as "DNS Name" in the portal, and **client secret credentials (client id, client secret, tenant id)**
28
28
to instantiate a client object.
29
29
30
30
Client secret credential authentication is being used in this getting started section but you can find more ways to authenticate with
@@ -69,15 +69,15 @@ environment variables. The following example shows a way to do this in Powershel
69
69
```
70
70
71
71
* Create the Managed HSM and grant the above mentioned service principal authorization to perform administrative operations on the Managed HSM
72
-
(replace `<your-resource-group-name>` and `<your-key-vault-name>` with your own, unique names and `<your-service-principal-object-id>` with the value from above):
72
+
(replace `<your-resource-group-name>` and `<your-managed-hsm-name>` with your own, unique names and `<your-service-principal-object-id>` with the value from above):
@@ -114,25 +114,24 @@ who are able to download a security domain and [manage roles for data plane acce
114
114
To perform other actions on keys, you need to assign principals to other roles such as "Managed HSM Crypto User", which can perform non-destructive key operations:
115
115
116
116
```PowerShell
117
-
az keyvault role assignment create --hsm-name <your-key-vault-name> --role "Managed HSM Crypto User" --scope / --assignee-object-id <principal-or-user-object-ID> --assignee-principal-type <principal-type>
117
+
az keyvault role assignment create --hsm-name <your-managed-hsm-name> --role "Managed HSM Crypto User" --scope / --assignee-object-id <principal-or-user-object-ID> --assignee-principal-type <principal-type>
118
118
```
119
119
120
120
Please read [best practices][best_practices] for properly securing your managed HSM.
121
121
122
122
#### Create KeyVaultAccessControlClient
123
-
Once you've populated the **AZURE_CLIENT_ID**, **AZURE_CLIENT_SECRET** and **AZURE_TENANT_ID** environment variables and replaced **your-vault-url**
124
-
with the above returned URI, you can create the [KeyVaultAccessControlClient][rbac_client]:
123
+
Once you've populated the **AZURE_CLIENT_ID**, **AZURE_CLIENT_SECRET**, and **AZURE_TENANT_ID** environment variables, replace **managedHsmUrl** with the output of `az keyvault show` in the example below to create the [KeyVaultAccessControlClient][rbac_client]
0 commit comments