Skip to content

Commit ccecfef

Browse files
Incorporating PM inputs
1 parent 9fe4e15 commit ccecfef

2 files changed

Lines changed: 18 additions & 18 deletions

File tree

93.7 KB
Loading

articles/azure-netapp-files/object-rest-api-access-configure.md

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -24,26 +24,30 @@ Azure NetApp Files now supports two certificate workflows for Object REST API ac
2424
1. Azure Key Vault–based certificates, which are created and selected by reference during bucket creation
2525
1. Direct certificate upload, where PEM certificates are generated locally and uploaded at bucket creation time.
2626

27+
### Using Azure Key Vault as the certificate source
2728

29+
When creating the certificate, ensure:
30+
31+
* the **Content Type** is set to PKCS#12
32+
* the **Subject** field is set to the IP address or fully qualified domain name (FQDN) of your Azure NetApp Files endpoint using the format `"CN=<IP or FQDN>"`
33+
* the **DNS Names** entry specifies the IP address or FQDN
34+
35+
### Upload the certificate manually
2836
<!-- DNS? -->
2937

30-
### [Portal](#tab/portal)
38+
#### [Portal](#tab/portal)
3139

3240
See the [Azure Key Vault documentation for adding a certificate to Key Vault](/azure//key-vault/certificates/quick-create-portal#add-a-certificate-to-key-vault).
3341

3442
When creating the certificate, ensure:
3543

36-
* the **Content Type** is set to PKCS#12
37-
38-
>NOTE
39-
>The PEM content type can still be used if the certificate is not stored in Azure Key Vault.
40-
44+
* the **Content Type** is set to PEM
4145
* the **Subject** field is set to the IP address or fully qualified domain name (FQDN) of your Azure NetApp Files endpoint using the format `"CN=<IP or FQDN>"`
4246
* the **DNS Names** entry specifies the IP address or FQDN
4347

4448
:::image type="content" source="./media/object-rest-api-access-configure/create-certificate.png" alt-text="Screenshot of create certificate options." lightbox="./media/object-rest-api-access-configure/create-certificate.png":::
4549

46-
### [Script](#tab/script)
50+
#### [Script](#tab/script)
4751

4852
This script creates a certificate locally. Set the computer name `CN=` to the IP address or fully qualified domain name (FQDN) of your object REST API-enabled endpoint. This script creates a folder that includes the necessary PEM file and private keys.
4953

@@ -101,24 +105,20 @@ To enable object REST API, you must create a bucket.
101105

102106
Select Read or Read-Write.
103107

104-
:::image type="content" source="./media/object-rest-api-access-configure/create-bucket.png" alt-text="Screenshot of create a bucket menu." lightbox="./media/object-rest-api-access-configure/create-bucket.png":::
105-
106-
1. If you haven't provided a certificate, you can do one of the following:
107-
108-
1. If the certificate was generated and stored in Key Vault, use the PKCS#12 certificate directly from the Azure Key Vault.
109-
110-
1. If the certificate was generated locally (PEM), upload the PEM file by providing the following information:
111-
112108
* **Fully qualified domain name**
113109

114110
Enter the fully qualified domain name.
115111

116-
* **Certificate source**
112+
:::image type="content" source="./media/object-rest-api-access-configure/create-bucket.png" alt-text="Screenshot of create a bucket menu." lightbox="./media/object-rest-api-access-configure/create-bucket.png":::
113+
114+
115+
1. For the **Certificate source**, you can do one of the following:
117116

118-
Upload the appropriate certificate. Only PEM files are supported.
117+
1. To use a certificate stored in the Azure Key Vault, select **Azure Key Vault** and use the PKCS#12 certificate directly from the Azure Key Vault.
119118

120-
Select **Save**.
119+
1. To upload the certificate manually, select **Upload Certificate** and upload the PEM) certificate.
121120

121+
122122
1. Select **Create**.
123123

124124
After you create a bucket, you need to generate credentials to access the bucket.

0 commit comments

Comments
 (0)