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: content/nginx-one/how-to/certificates/manage-certificates.md
+13-6Lines changed: 13 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,10 +14,17 @@ weight: 100
14
14
15
15
This guide explains how you can manage SSL/TLS certificates with the F5 NGINX One Console. Valid certificates support encrypted connections between NGINX and your users.
16
16
17
-
You may have separate sets of SSL/TLS certificates for:
18
-
- Deployments of NGINX, to support secure web services
19
-
- For more information on how you can use these certificates to secure your servers, see the section on [NGINX SSL termination]({{< relref "/nginx/admin-guide/security-controls/terminating-ssl-http.md" >}}).
| 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. |
24
+
25
+
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.
26
+
Find the `config_dirs` parameter in that file, as described in the NGINX Agent [Basic configuration]({{< relref "/nginx-agent/configuration/configuration-overview.md/#cli-flags-and-environment-variables" >}})
27
+
You may need to add a directory like `/etc/ssl` to that parameter.
21
28
22
29
From the NGINX One Console you can:
23
30
@@ -42,7 +49,7 @@ If you are managing the certificate from NGINX One Console, we recommend that yo
42
49
Before you add and manage certificates with the NGINX One Console make sure:
43
50
44
51
- You have access to the NGINX One Console
45
-
- You have access through the F5 Distributed Cloud role, as described in the [Authentication]({{< relref "../../api/authentication.md" >}}) guide, to manage SSL/TLS certificates
52
+
- You have access through the F5 Distributed Cloud role, as described in the [Authentication]({{< relref "/nginx-one/api/authentication.md" >}}) guide, to manage SSL/TLS certificates
46
53
- You have the `f5xc-nginx-one-user` role for your account
47
54
- Your SSL/TLS certificates and keys match
48
55
@@ -154,7 +161,7 @@ If that certificate is managed and is part of a Config Sync Group, that change a
154
161
155
162
## Managed and unmanaged certificates
156
163
157
-
If you register an instance to NGINX One Console, as described in [Add your NGINX instances to NGINX One]({{< relref "../../getting-started.md#add-your-nginx-instances-to-nginx-one" >}}), and the associated SSL/TLS certificates:
164
+
If you register an instance to NGINX One Console, as described in [Add your NGINX instances to NGINX One]({{< relref "/nginx-one/getting-started.md#add-your-nginx-instances-to-nginx-one" >}}), and the associated SSL/TLS certificates:
158
165
159
166
- Are used in their NGINX configuration
160
167
- Do _not_ match an existing managed SSL certificate/CA bundle
0 commit comments