Skip to content

Commit 906328e

Browse files
authored
Merge pull request #186631 from atikmapari/Broken-link-sebansal
Broken link fixed
2 parents 99ff452 + 8e2b7e3 commit 906328e

7 files changed

+9
-9
lines changed

articles/key-vault/certificates/certificate-access-control.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ ms.author: sebansal
3838
- Permissions for privileged operations
3939
- **purge**: Purge (permanently delete) a deleted certificate
4040

41-
For more information, see the [Certificate operations in the Key Vault REST API reference](/rest/api/keyvault). For information on establishing permissions, see [Vaults - Update Access Policy](/rest/api/keyvault/vaults/updateaccesspolicy).
41+
For more information, see the [Certificate operations in the Key Vault REST API reference](/rest/api/keyvault). For information on establishing permissions, see [Vaults - Update Access Policy](/rest/api/keyvault/keyvault/vaults/update-access-policy).
4242

4343
## Troubleshoot
4444
You may see error due to missing access policy. For example ```Error type : Access denied or user is unauthorized to create certificate```

articles/key-vault/certificates/create-certificate-signing-request.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -145,5 +145,5 @@ Example
145145
- [Authentication, requests, and responses](../general/authentication-requests-and-responses.md)
146146
- [Key Vault Developer's Guide](../general/developers-guide.md)
147147
- [Azure Key Vault REST API reference](/rest/api/keyvault)
148-
- [Vaults - Create or Update](/rest/api/keyvault/vaults/createorupdate)
149-
- [Vaults - Update Access Policy](/rest/api/keyvault/vaults/updateaccesspolicy)
148+
- [Vaults - Create or Update](/rest/api/keyvault/keyvault/vaults/create-or-update)
149+
- [Vaults - Update Access Policy](/rest/api/keyvault/keyvault/vaults/update-access-policy)

articles/key-vault/certificates/how-to-export-certificate.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ After a Key Vault certificate is created, you can retrieve it from the addressab
3232
- **Exportable**: The policy used to create the certificate indicates the key is exportable.
3333
- **Non-exportable**: The policy used to create the certificate indicates the key is non-exportable. In this case, the private key isn't part of the value when it's retrieved as a secret.
3434

35-
Supported keytypes: RSA, RSA-HSM, EC, EC-HSM, oct (listed [here](/rest/api/keyvault/createcertificate/createcertificate#jsonwebkeytype))
35+
Supported keytypes: RSA, RSA-HSM, EC, EC-HSM, oct (listed [here](/rest/api/keyvault/certificates/create-certificate/create-certificate#jsonwebkeytype))
3636
Exportable is only allowed with RSA, EC. HSM keys would be non-exportable.
3737

3838
See [About Azure Key Vault certificates](./about-certificates.md#exportable-or-non-exportable-key) for more information.

articles/key-vault/certificates/how-to-integrate-certificate-authority.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -168,7 +168,7 @@ Error message: "Please perform a merge to complete this certificate request."
168168

169169
Merge the CSR signed by the certificate authority to complete the request. For information about merging a CSR, see [Create and merge a CSR](./create-certificate-signing-request.md).
170170

171-
For more information, see [Certificate 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).
171+
For more information, see [Certificate 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).
172172

173173
## Frequently asked questions
174174

articles/key-vault/certificates/import-cert-faqs.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ sections:
5959
answer: |
6060
Each certificate name must be unique. A certificate with the same name might be in a soft-deleted state. Also, according to the [composition of a certificate](./about-certificates.md#composition-of-a-certificate), when new certificate is created, it creates an addressable secret with the same name so if there's another key or secret in the key vault with the same name as the one you're trying to specify for your certificate, the certificate creation will fail and you'll need to either remove that key or secret or use a different name for your certificate.
6161
62-
For more information, see [Get Deleted Certificate operation](/rest/api/keyvault/getdeletedcertificate/getdeletedcertificate).
62+
For more information, see [Get Deleted Certificate operation](/rest/api/keyvault/certificates/get-deleted-certificate/get-deleted-certificate).
6363
6464
- question: |
6565
Why am I getting "Error type: char length is too long"?

articles/key-vault/certificates/tutorial-import-certificate.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -149,5 +149,5 @@ When no longer needed, delete the resource group, which deletes the Key Vault an
149149
In this tutorial, you created a Key Vault and imported a certificate in it. To learn more about Key Vault and how to integrate it with your applications, continue on to the articles below.
150150

151151
- Read more about [Managing certificate creation in Azure Key Vault](./create-certificate-scenarios.md)
152-
- See examples of [Importing Certificates Using REST APIs](/rest/api/keyvault/importcertificate/importcertificate)
152+
- See examples of [Importing Certificates Using REST APIs](/rest/api/keyvault/certificates/import-certificate/import-certificate)
153153
- Review the [Key Vault security overview](../general/security-features.md)

articles/key-vault/keys/quick-create-template.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -166,8 +166,8 @@ More Azure Key Vault template samples can be found in [Azure Quickstart Template
166166
|Parameter |Definition |
167167
|---------|---------|
168168
|**keyOps** | Specifies operations that can be performed by using the key. If you don't specify this parameter, all operations can be performed. The acceptable values for this parameter are a comma-separated list of key operations as defined by the [JSON Web Key (JWK) specification](https://tools.ietf.org/html/draft-ietf-jose-json-web-key-41): <br> `["sign", "verify", "encrypt", "decrypt", " wrapKey", "unwrapKey"]` |
169-
|**CurveName** | Elliptic curve (EC) name for EC key type. See [JsonWebKeyCurveName](/rest/api/keyvault/createkey/createkey#jsonwebkeycurvename) |
170-
|**Kty** | The type of key to create. For valid values, see [JsonWebKeyType](/rest/api/keyvault/createkey/createkey#jsonwebkeytype) |
169+
|**CurveName** | Elliptic curve (EC) name for EC key type. See [JsonWebKeyCurveName](/rest/api/keyvault/keys/create-key/create-key#jsonwebkeycurvename) |
170+
|**Kty** | The type of key to create. For valid values, see [JsonWebKeyType](/rest/api/keyvault/keys/create-key/create-key#jsonwebkeytype) |
171171
|**Tags** | Application-specific metadata in the form of key-value pairs. |
172172
|**nbf** | Specifies the time, as a DateTime object, before which the key can't be used. The format would be Unix time stamp (the number of seconds after Unix Epoch on January 1st, 1970 at UTC). |
173173
|**exp** | Specifies the expiration time, as a DateTime object. The format would be Unix time stamp (the number of seconds after Unix Epoch on January 1st, 1970 at UTC). |

0 commit comments

Comments
 (0)