Skip to content

Subscription renewals: review and clarify JWT license file handling for subscription renewal #162

Open
@travisamartin

Description

@travisamartin

Description

A customer provided feedback on the About subscription licenses documentation. They rated the content 6/7 for helpfulness but requested additional clarity on handling JWT license files for subscription renewals.

Customer feedback

For complete operational guidelines on license.jwt, it would be great to advise:

  1. For NGINX Plus instances running on an expiring subscription, do we just copy the new JWT to /etc/nginx/license.jwt, and will NGINX Plus start reporting usage to NIM under the new subscription ID?
  2. For renewed subscriptions (with a new subscription ID), does this process involve:
    • Downloading the new subscription's JWT license file
    • Uploading the JWT to the instance manager
    • Copying the new JWT to the running NGINX instance
    • Restarting/reloading NGINX?
  3. Does NIM require license.jwt itself on an active subscription?
  4. Does NIM support proxy servers in disconnected mode, or is there a separate process to upload usage reports from NIM to F5 over the proxy server?

Acceptance criteria

  • Review the existing doc to confirm whether it already addresses these questions
  • If the doc fully covers these points, ensure the explanations are clear and easy to find
  • If updates are needed, clarify:
    • How to apply a new license.jwt file
    • Whether a restart or reload is required
    • Whether NIM requires license.jwt on an active subscription
    • How proxy servers work for NIM in disconnected mode

The customer provided contact info and is open to being contacted. Consider following up, if appropriate.

Label

customer-feedback

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions