Skip to content

Commit a227b5b

Browse files
authored
Merge branch 'main' into ps-dev-waf-dir
2 parents a4c7f7d + 422733b commit a227b5b

File tree

1 file changed

+30
-0
lines changed
  • content/nginxaas-azure/getting-started/ssl-tls-certificates

1 file changed

+30
-0
lines changed

content/nginxaas-azure/getting-started/ssl-tls-certificates/overview.md

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -319,3 +319,33 @@ The following section describes common errors you might encounter while adding S
319319
az keyvault certificate set-attributes --enabled true --id $certificate_id
320320
```
321321
</details>
322+
323+
#### Error code: `NoCertificateContent`
324+
325+
**Description:** No certificate was found when parsing the file.
326+
327+
**Resolution:** Ensure the file is not empty and contains properly formatted PEM or PKCS12 certificate data.
328+
329+
#### Error code: `MissingContentType`
330+
331+
**Description:** The retrieved secret is missing the *contentType* field.
332+
333+
**Resolution:** When creating an [Azure certificate](https://learn.microsoft.com/en-us/azure/key-vault/certificates/about-certificates) in key vault, the *contentType* field will be properly set to either *application/x-pem-file* or *application/x-pkcs12*. If a certificate is added as a generic [Azure secret](https://learn.microsoft.com/en-us/azure/key-vault/secrets/about-secrets) the *contentType* field must be manually set to help with interpreting the secret data when it is retrieved. We recommend creating a certificate object, instead of a secret object containing certificate data, to ensure proprer formatting and *contentType*.
334+
335+
#### Error code: `UnrecognizedContentType`
336+
337+
**Description:** The retrieved secret's content type, as interpreted from the *contentType* field, is of an unsupported type.
338+
339+
**Resolution:** When creating an [Azure certificate](https://learn.microsoft.com/en-us/azure/key-vault/certificates/about-certificates) in key vault, the *contentType* field will be properly set to either *application/x-pem-file* or *application/x-pkcs12*. NGINXaaS does not support other content types added as generic [Azure secrets](https://learn.microsoft.com/en-us/azure/key-vault/secrets/about-secrets). Ensure the provided certificate is either a PEM or PKCS12 [Azure certificate](https://learn.microsoft.com/en-us/azure/key-vault/certificates/about-certificates).
340+
341+
#### Error code: `PKCS12ParseFailure`
342+
343+
**Description:** The PKCS12 certificate could not be parsed.
344+
345+
**Resolution:** Ensure the file is not empty and contains properly formatted PKCS12 certificate data.
346+
347+
#### Error code: `PEMParseFailure`
348+
349+
**Description:** The PEM certificate could not be parsed.
350+
351+
**Resolution:** Ensure the file is not empty and contains properly formatted PEM certificate data.

0 commit comments

Comments
 (0)