Update license includes to be generic and applicable to all products

[ADubhlaoich]

Overview

As a reader, I want instructions about my license files to be identical, So I can use existing knowledge when activating a commercial subscription.

Description

NGINX products with commercial support all go through the same initial steps during set-up:

• Log into My F5
• Download certificate files
• Transform certificate files into usable tokens

With the consolidation of all documentation sets into one repository, this is a relatively straightforward use case for include re-use.

A good starting point is the licenses-and-reporting includes folder, which encapsulates most of this type of content.

This can likely be turned into a full section of text, meaning that each individual page will have a header and a single include to add necessary detail.

Acceptance criteria

• Update the relevant includes to be generic, and applicable to any product integration
• Add the includes to products and pages that do not currently use them
• Ensure that each usage of the include still has the full context required to complete the task outlined in the document

[mjang]

Note: this is not related to the BSD license for this repository.

[mjang]

One missing detail (or at least something I can't find): the role of the SSL cert with our licenses.

When a user follows https://docs.nginx.com/solutions/about-subscription-licenses/ for licenses, they need to download:

• License key (which gets named license.jwt)
• SSL certificate
• SSL key

The SSL certs and keys are different from the SSL certs and keys used to encrypt NGINX communications, such as for web services.

[github-actions]

This issue is stale because it has been open for 90 days with no activity. Remove the stale label or add a comment to keep it open. If you do not take action, this will be closed in 10 days.

[github-actions]

This issue was closed after 100 days of inactivity.