NIM release 2.21.0 (#1416)

NIM release 2.21.0 (#272)

* updated docs for bot signatures

* Reorganized the NIM WAF docs

Author: travisamartin

content/includes/agent/installation/install-agent-api.md

@@ -1,7 +1,7 @@
 ---
 nd-docs: DOCS-1031
 files:
-  - content/nim/nginx-app-protect/setup-waf-config-management.md
+  - content/nim/waf-integration/configuration/setup-waf-config-management.md
 ---
 
 {{< call-out "note" >}}Make sure `gpg` is installed on your system before continuing. You can install NGINX Agent using command-line tools like `curl` or `wget`.{{< /call-out >}}

content/includes/nim/admin-guide/auth/basic-auth-api-requests.md

@@ -4,13 +4,13 @@ nd-docs: DOCS-1295
 
 To use basic authentication for API requests, include your base64-encoded credentials as a "Basic" token in the "Authorization" header. To create the base64-encoded credentials, run the following command:
 
-```bash
+```shell
 echo -n <username>:<password> | base64
 ```
 
 Once you've generated the credentials, you can include them in your API request. Here's how to do it with `curl`:
 
-```bash
+```shell
 curl -X GET "https://<NIM_FQDN>/api/platform/<API_VERSION>/systems" -H "Authorization: Basic <base64_encoded_credentials>"
 ```
 

content/includes/nim/disconnected/set-mode-of-operation-disconnected.md

@@ -12,6 +12,6 @@ nd-docs: "DOCS-1663"
 
 2.	Restart NGINX Instance Manager:
 
-    ``` bash
+    ```shell
     sudo systemctl restart nms
     ```

content/includes/nim/docker/docker-registry-login.md

@@ -12,7 +12,7 @@ nd-docs: "DOCS-1666"
 
 2. Log in to the Docker registry using the contents of the JSON Web Token file:
 
-   ```bash
+   ```shell
    docker login private-registry.nginx.com --username=<JWT_CONTENTS> --password=none
    ```
 

content/includes/nim/how-to-access-api-docs.md

@@ -2,8 +2,8 @@
 nd-docs: DOCS-991
 ---
 
-You can access the NGINX Instance Manager API documentation from the web interface:
+Access the NGINX Instance Manager API documentation from the web interface:
 
-1. Log in to the FQDN of your NGINX Instance Manager host.
-2. Select **API Documentation** from the Launchpad menu.
-3. On the left menu, select **NIM and Platform API**.
+1. Go to the FQDN of your NGINX Instance Manager host and log in.  
+2. From the Launchpad menu, select **API Documentation**.  
+3. In the left menu, choose **NIM and Platform API**.

content/includes/nim/how-to-access-nim-api.md

@@ -2,4 +2,6 @@
 nd-docs: DOCS-1050
 ---
 
-You can use tools like `curl` or [Postman](https://www.postman.com) to interact with the NGINX Instance Manager REST API. The API URL is `https://<NIM-FQDN>/api/[nim|platform]/<API_VERSION>`, and each request requires authentication. For more details on authentication options, see the [API Overview]({{< ref "/nim/fundamentals/api-overview.md" >}}).
+Use tools such as `curl` or [Postman](https://www.postman.com) to send requests to the NGINX Instance Manager REST API.
+The API base URL is `https://<NIM-FQDN>/api/[nim|platform]/<API_VERSION>`.  
+All requests require authentication. For details on authentication methods, see the [API overview]({{< ref "/nim/fundamentals/api-overview.md" >}}).

content/includes/nim/kubernetes/access-webui-helm.md

@@ -6,7 +6,7 @@ You can access the NGINX Instance Manager web interface using the external IP ad
 
 1. To look up the external IP address for the API Gateway, run the following command:
 
-   ```bash
+   ```shell
    kubectl -n nim get svc apigw
    ```
 

content/includes/nim/security-monitoring/update-security-monitoring-attack-signature-database.md

@@ -0,0 +1,26 @@
+---
+docs:
+files:
+  - /nim/security-monitoring/update-signatures.md
+---
+
+1. Open an SSH connection to the data plane host and log in.
+1. Generate a Signature Report file using the [Attack Signature Report Tool]({{< ref "/waf/configure/converters.md#attack-signature-report-tool" >}}). Save the file as `signature-report.json`:
+
+    ```shell
+    sudo /opt/app_protect/bin/get-signatures -o ./signature-report.json
+    ```
+
+1. Open an SSH connection to the management plane host and log in.
+1. Copy the `signature-report.json` file to the NGINX Instance Manager control plane at `/usr/share/nms/sigdb/`:
+
+    ```shell
+    sudo scp /path/to/signature-report.json {user}@{host}:/usr/share/nms/sigdb/signature-report.json
+    ```
+
+1. Restart the NGINX Instance Manager services to apply the update:
+
+    ```shell
+    sudo systemctl restart nms-ingestion
+    sudo systemctl restart nms-core
+    ```

content/includes/nim/system-configuration/trust-proxy-ca-certificates.md

@@ -6,7 +6,7 @@
 
     - **Debian/Ubuntu**:
 
-       ```bash
+       ```shell
        sudo update-ca-certificates
        ``` 
 

content/includes/nim/tech-specs/nim-app-protect-support.md

@@ -2,13 +2,13 @@
 nd-docs: DOCS-1068
 ---
 
-NGINX Instance Manager supports the following versions of [F5 WAF for NGINX](https://docs.nginx.com/nginx-app-protect/):
+NGINX Instance Manager supports the following versions of [F5 WAF for NGINX](https://docs.nginx.com/waf/):
 
-{{<bootstrap-table "table table-striped table-bordered">}}
+{{< table >}}
 
-| NGINX Instance Manager | F5 WAF for NGINX              |
-|------------------------|------------------------------------|
-| 2.17.0–2.20.0          | Release 4.8.0–4.16.0, 5.1.0–5.9.0 |
+| NGINX Instance Manager | F5 WAF for NGINX                  |
+| ---------------------- | --------------------------------- |
+| 2.17.0–2.21.0          | Release 4.8.0–4.16.0, 5.1.0–5.9.0 |
 | 2.15.1–2.16.0          | Release 4.8.0–4.10.0              |
 | 2.14.1–2.15.0          | Release 4.4.0–4.7.0               |
 | 2.13.0–2.14.0          | Release 4.3.0–4.5.0               |
@@ -20,5 +20,4 @@ NGINX Instance Manager supports the following versions of [F5 WAF for NGINX](htt
 | 2.7.0                  | Release 3.12.2–4.0.0              |
 | 2.6.0                  | Release 3.12.2                    |
 
-{{</bootstrap-table>}}
-
+{{</ table >}}