Skip to content

Commit acad945

Browse files
committed
More
1 parent e4c20c3 commit acad945

File tree

5 files changed

+53
-28
lines changed

5 files changed

+53
-28
lines changed
Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
docs:
3+
---
4+
5+
With this option, You can incorporate [Managed certificates]({{< relref "/nginx-one/how-to/certificates/manage-certificates.md#managed-and-unmanaged-certificates" >}}).
6+
In the **Choose Certificate** drop-down, select the managed certificate of your choice, and select **Add**. You can then:
7+
8+
1. Review details of the certificate. The next steps depend on whether the certificate is a CA bundle or a certificate / key pair.
9+
1. Enter the **Certificate File Path**, such as `/etc/ssl/nginx/mycert.crt` or `/etc/ssl/nginx/mycert.pem`.
10+
1. If you selected a key pair, you'll also enter the **Key File Path**, such as `/etc/ssl/nginx/mycert.key`.
11+
1. If you select **Add Item**, you can add the same certificate or key to another directory.
12+
1. Select **Add**. You should now be returned to the **Edit Configuration** window.
13+
You should now see the files you specified in the directory tree.
14+
1. Select **Next** and then **Save and Publish**.
15+
You may see a message that suggests publication is in progress.
16+
1. When publication is complete, you're taken back to the **Configuration** tab. You should see the updated configuration in the window.

content/includes/nginx-one/add-file/new-ssl-bundle.md

Lines changed: 17 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,23 @@ You can add certificates in the following formats:
1111
- **SSL Certificate and Key**
1212
- **CA Certificate Bundle**
1313

14-
In each case, you can upload files directly, or enter the content of the certificates in a text box. Once you upload these certificates, you'll see:
14+
In each case, you can upload files directly, or enter the content of the certificates in a text box. Once you upload these certificates, you may need to scroll down. You'll see:
1515

1616
- **Certificate Details**, with the Subject Name, start and end dates.
1717
- **Key Details**, with the encryption key size and algorithm, such as RSA
18+
19+
Select **Save and Continue**. You're taken to another screen where you can specify the locations for your files, which may be:
20+
21+
- **Certificate File Path**
22+
- Enter the full path to your certificate, such as
23+
- /etc/ssl/nginx/server.crt
24+
- /etc/ssl/nginx/server.pem
25+
26+
- **Key File Path**
27+
- Enter the full path to your certificate key, such as
28+
- /etc/ssl/nginx/server.key
29+
- If you're using a `.pem` file, you won't have a separate key.
30+
31+
With the **Add Item** button, you can add the file to additional directories.
32+
33+
When complete, select **Add** to include the certificate files that you've configured to desired directories.

content/nginx-one/how-to/certificates/manage-certificates.md

Lines changed: 17 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -16,11 +16,13 @@ This guide explains how you can manage SSL/TLS certificates with the F5 NGINX On
1616

1717
You may have separate sets of SSL/TLS certificates, as described in the following table:
1818

19+
{{<bootstrap-table "table table-striped table-bordered">}}
1920
| Functionality | Typical file names | Notes |
2021
|-------------------|--------------------------------------------------------------------|----------------------------------------------------------------------------------------|
21-
| Website traffic | /etc/nginx/ssl/example.com.crt <br> /etc/nginx/ssl/example.com.key | Typically purchased from a Certificate Authority (CA). |
22-
| Repository access | /etc/ssl/nginx/nginx-repo.crt <br> /etc/ssl/nginx/nginx-repo.key | Supports access to repositories to download and install NGINX packages. |
23-
| NGINX Licensing | /etc/ssl/nginx/server.crt <br> /etc/ssl/nginx/server.key | Supports access to repositories. Based on licenses downloaded from https://my.f5.com/. Time limited. |
22+
| Website traffic | /etc/nginx/ssl/example.com.crt <br> /etc/nginx/ssl/example.com.key | Typically purchased from a Certificate Authority (CA) |
23+
| Repository access | /etc/ssl/nginx/nginx-repo.crt <br> /etc/ssl/nginx/nginx-repo.key | Supports access to repositories to download and install NGINX packages |
24+
| NGINX Licensing | /etc/ssl/nginx/server.crt <br> /etc/ssl/nginx/server.key | Supports access to repositories. Based on licenses downloaded from https://my.f5.com/ |
25+
{{</bootstrap-table>}}
2426

2527
Allowed directories depend on the [NGINX Agent]({{< relref "/nginx-one/getting-started/#install-nginx-agent" >}}). Look for the `/etc/nginx-agent/nginx-agent.conf` file.
2628
Find the `config_dirs` parameter in that file, as described in the NGINX Agent [Basic configuration](https://docs.nginx.com/nginx-agent/configuration/configuration-overview/#cli-flags--environment-variables).
@@ -65,7 +67,18 @@ The NGINX One Console allows you to upload these certificates as text and as fil
6567
Make sure your certificates, keys, and pem files are encrypted to one of the following standards:
6668

6769
- RSA
68-
- ECDSA
70+
- ECC/ECDSA
71+
72+
In other words, any private key of this type should be supported, regardless of the curve types or hashing algorithm.
73+
74+
For exmaple, if you use ECDSA private keys in PEM format, the PEM headers should contain:
75+
76+
```
77+
-----BEGIN EC PRIVATE KEY-----
78+
<...base64-encoded key>
79+
-----END EC PRIVATE KEY-----
80+
81+
```
6982

7083
If you use one of these keys, the US National Institute of Standards and Technology, in [Publication 800-57 Part 3 (PDF)](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-57Pt3r1.pdf), recommends a key size of at least
7184
2048 bits. It also has recommnedations for ECDSA.

content/nginx-one/how-to/config-sync-groups/add-file-csg.md

Lines changed: 2 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ doctypes:
44
- task
55
tags:
66
- docs
7-
title: Add a file in a Config Sync Group
7+
title: Add a file to a Config Sync Group
88
toc: true
99
weight: 400
1010
---
@@ -60,17 +60,8 @@ Enter the name of the desired configuration file, such as `abc.conf` and select
6060

6161
### Existing SSL Certificate or CA Bundle
6262

63+
{{< include "nginx-one/add-file/existing-ssl-bundle.md" >}}
6364
With this option, You can incorporate [Managed certificates]({{< relref "/nginx-one/how-to/certificates/manage-certificates.md#managed-and-unmanaged-certificates" >}}).
64-
In the **Choose Certificate** drop-down, select the managed certificate of your choice, and select **Add**. You can then:
65-
66-
1. Review details of the certificate. The next steps depend on whether the certificate is a CA bundle or a certificate / key pair.
67-
1. Enter the **Certificate File Path**, such as `/etc/ssl/nginx/mycert.crt`.
68-
1. If you selected a key pair, you'll also enter the **Key File Path**, such as `/etc/ssl/nginx/mycert.key`.
69-
1. Select **Add**. You should now be returned to the **Edit Configuration** window.
70-
You should now see the files you specified in the directory tree.
71-
1. Select **Next** and then **Save and Publish**.
72-
You may see a message that suggests publication is in progress.
73-
1. When publication is complete, you're taken back to the **Configuration** tab. You should see the updated configuration in the window.
7465

7566
## See also
7667

content/nginx-one/how-to/nginx-configs/add-file.md

Lines changed: 1 addition & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -61,18 +61,7 @@ Enter the name of the desired configuration file, such as `abc.conf` and select
6161

6262
### Existing SSL Certificate or CA Bundle
6363

64-
With this option, You can incorporate [Managed certificates]({{< relref "/nginx-one/how-to/certificates/manage-certificates.md#managed-and-unmanaged-certificates" >}}).
65-
In the **Choose Certificate** drop-down, select the managed certificate of your choice, and select **Add**. You can then:
66-
67-
1. Review details of the certificate. The next steps depend on whether the certificate is a CA bundle or a certificate / key pair.
68-
1. Enter the **Certificate File Path**, such as `/etc/ssl/nginx/mycert.crt`.
69-
1. If you selected a key pair, you'll also enter the **Key File Path**, such as `/etc/ssl/nginx/mycert.key`.
70-
1. Select **Add**. You should now be returned to the **Edit Configuration** window.
71-
You should now see the files you specified in the directory tree.
72-
1. Select **Next** and then **Save and Publish**.
73-
You may see a message that suggests publication is in progress.
74-
- If the instance is offline, **Save and Publish** does not work.
75-
1. When publication is complete, you're taken back to the **Configuration** tab. You should see the updated configuration in the window.
64+
{{< include "nginx-one/add-file/existing-ssl-bundle.md" >}}
7665

7766
## See also
7867

0 commit comments

Comments
 (0)