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: articles/key-vault/certificates/about-certificates.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ The addressable key becomes more relevant with non-exportable KV certificates. T
41
41
42
42
The type of key pair to supported for certificates
43
43
44
-
- Supported keytypes: RSA, RSA-HSM, EC, EC-HSM, oct (listed [here](/rest/api/keyvault/createcertificate/createcertificate#jsonwebkeytype))
44
+
- Supported keytypes: RSA, RSA-HSM, EC, EC-HSM, oct (listed [here](/rest/api/keyvault/certificates/create-certificate/create-certificate#jsonwebkeytype))
45
45
Exportable is only allowed with RSA, EC. HSM keys would be non-exportable.
46
46
47
47
|Key type|About|Security|
@@ -91,7 +91,7 @@ At a high level, a certificate policy contains the following information (their
91
91
92
92
- X509 certificate properties: Contains subject name, subject alternate names, and other properties used to create an x509 certificate request.
93
93
- Key Properties: contains key type, key length, exportable, and ReuseKeyOnRenewal fields. These fields instruct key vault on how to generate a key.
94
-
- Supported keytypes: RSA, RSA-HSM, EC, EC-HSM, oct (listed [here](/rest/api/keyvault/createcertificate/createcertificate#jsonwebkeytype))
94
+
- Supported keytypes: RSA, RSA-HSM, EC, EC-HSM, oct (listed [here](/rest/api/keyvault/certificates/create-certificate/create-certificate#jsonwebkeytype))
95
95
- Secret properties: contains secret properties such as content type of addressable secret to generate the secret value, for retrieving certificate as a secret.
96
96
- Lifetime Actions: contains lifetime actions for the KV Certificate. Each lifetime action contains:
Copy file name to clipboardExpand all lines: articles/key-vault/certificates/certificate-scenarios.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,14 +41,14 @@ Certificates are composed of three interrelated resources linked together as a K
41
41
42
42
**Step 3** - A Contoso admin, along with a Contoso employee (Key Vault user) who owns certificates, depending on the CA, can get a certificate from the admin or directly from the account with the CA.
43
43
44
-
- Begin an add credential operation to a key vault by [setting a certificate issuer](/rest/api/keyvault/setcertificateissuer/setcertificateissuer) resource. A certificate issuer is an entity represented in Azure Key Vault (KV) as a CertificateIssuer resource. It is used to provide information about the source of a KV certificate; issuer name, provider, credentials, and other administrative details.
44
+
- Begin an add credential operation to a key vault by [setting a certificate issuer](/rest/api/keyvault/certificates/set-certificate-issuer/set-certificate-issuer) resource. A certificate issuer is an entity represented in Azure Key Vault (KV) as a CertificateIssuer resource. It is used to provide information about the source of a KV certificate; issuer name, provider, credentials, and other administrative details.
45
45
- Ex. MyDigiCertIssuer
46
46
- Provider
47
47
- Credentials – CA account credentials. Each CA has its own specific data.
48
48
49
49
For more information on creating accounts with CA Providers, see the related post on the [Key Vault blog](/archive/blogs/kv/manage-certificates-via-azure-key-vault).
50
50
51
-
**Step 3.1** - Set up [certificate contacts](/rest/api/keyvault/setcertificatecontacts/setcertificatecontacts) for notifications. This is the contact for the Key Vault user. Key Vault does not enforce this step.
51
+
**Step 3.1** - Set up [certificate contacts](/rest/api/keyvault/certificates/set-certificate-contacts/set-certificate-contacts) for notifications. This is the contact for the Key Vault user. Key Vault does not enforce this step.
52
52
53
53
Note - This process, through step 3.1, is a onetime operation.
54
54
@@ -73,7 +73,7 @@ Note - This process, through step 3.1, is a onetime operation.
73
73
- Renewal information - > ex. 90 days before expiry
74
74
75
75
- A certificate creation process is usually an asynchronous process and involves polling your key vault for the state of the create certificate operation.
- Status: completed, failed with error information or, canceled
78
78
- Because of the delay to create, a cancel operation can be initiated. The cancel may or may not be effective.
79
79
@@ -112,7 +112,7 @@ When you are importing the certificate, you need to ensure that the key is inclu
112
112
113
113
### Formats of Merge CSR we support
114
114
AKV supports 2 PEM based formats. You can either merge a single PKCS#8 encoded certificate or a base64 encoded P7B (chain of certificates signed by CA).
115
-
If you need to covert the P7B's format to the supported one, you can use [certutil -encode](https://docs.microsoft.com/windows-server/administration/windows-commands/certutil#-encode)
115
+
If you need to covert the P7B's format to the supported one, you can use [certutil -encode](/windows-server/administration/windows-commands/certutil#-encode)
Copy file name to clipboardExpand all lines: articles/key-vault/keys/about-keys-details.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -163,7 +163,7 @@ The following permissions can be granted, on a per user / service principal basi
163
163
- Permissions for privileged operations
164
164
-*purge*: Purge (permanently delete) a deleted key
165
165
166
-
For more information on working with keys, see [Key operations in the Key Vault REST API reference](/rest/api/keyvault). For information on establishing permissions, see [Vaults - Create or Update](/rest/api/keyvault/vaults/createorupdate) and [Vaults - Update Access Policy](/rest/api/keyvault/vaults/updateaccesspolicy).
166
+
For more information on working with keys, see [Key operations in the Key Vault REST API reference](/rest/api/keyvault). For information on establishing permissions, see [Vaults - Create or Update](/rest/api/keyvault/keyvault/vaults/create-or-update) and [Vaults - Update Access Policy](/rest/api/keyvault/keyvault/vaults/update-access-policy).
Copy file name to clipboardExpand all lines: articles/key-vault/secrets/about-managed-storage-account-keys.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,7 @@ The following permissions can be used when authorizing a user or application pri
58
58
- Permissions for privileged operations
59
59
-*purge*: Purge (permanently delete) a managed storage account
60
60
61
-
For more information, see the [Storage account operations in the Key Vault REST API reference](/rest/api/keyvault). For information on establishing permissions, see [Vaults - Create or Update](/rest/api/keyvault/vaults/createorupdate) and [Vaults - Update Access Policy](/rest/api/keyvault/vaults/updateaccesspolicy).
61
+
For more information, see the [Storage account operations in the Key Vault REST API reference](/rest/api/keyvault). For information on establishing permissions, see [Vaults - Create or Update](/rest/api/keyvault/vaults/createorupdate) and [Vaults - Update Access Policy](/rest/api/keyvault/keyvault/vaults/update-access-policy).
0 commit comments