Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

License Activation and Verification: Key Format Description, Activation Interface, and Troubleshooting Steps for Activation Failures

Regarding Licenses, public sources confirm the activation method, online / offline modes, namespace binding, and the requirement to restart the enterprise service after activation.

A key point of this training content is to clearly separate “what can be confirmed from public sources” from “what needs internal supplementation.” Public documentation is sufficient to support a first version of activation process training, including online / offline activation, the need to switch licenseMode for offline mode, the requirement to restart dify-enterprise after activation, and the namespace binding relationship. However, public sources do not fully disclose the internal format of the License Key, the commercial issuance process, or certain backend fields.

1. License Activation Boundaries Confirmed by Public Sources

1. Activation Is Part of the Deployment Process, Not a Standalone Action

The official documentation explicitly places activation after Enterprise Dashboard initialization and deployment steps. This means training must present “deployment complete -> dashboard initialization -> License activation” as a continuous chain.

2. Both Online and Offline Processes Are Publicly Confirmed

The public documentation provides two process flows:

  • Online activation: Enter the License ID
  • Offline activation: Switch licenseMode, copy the Cluster ID, fill in the Offline Code

3. Verification Should Include Status Confirmation and Service Restart

The official documentation explicitly states that a restart of dify-enterprise is required after activation or refresh. Therefore, training should not treat “seeing the activated status” as the end point but should also verify that the service has taken effect.

2. Known Public Information

  • Supports both online and offline activation
  • Offline mode requires switching licenseMode in values.yaml
  • Restart of dify-enterprise is required after activation
  • License is bound to the namespace
  1. Log in to the Enterprise Dashboard
  2. Check the License status
  3. Confirm whether features are active according to the license
  4. Restart enterprise and verify that the status persists

4. Activation Failure Troubleshooting

  • Is the namespace consistent with expectations
  • Does the network allow online activation
  • Does the offline code match the current Cluster ID
  • Has the enterprise service been restarted

5. Sections Requiring Your Input

Public sources do not sufficiently disclose the internal format details of the License Key or complete activation interface fields. If your internal training needs to cover these, please add de-identified Key samples, Enterprise backend screenshots, or a formal SOP to this document.

Public Source References

note.com

  • No particularly strong direct matches on note.com at this time. Enterprise official License documentation is the more appropriate basis.

zenn.dev / Official Documentation / Other Public Pages

  • License Activation - Dify Enterprise Docs | https://enterprise-docs.dify.ai/versions/3-0-x/en-us/deployment/license-activation
  • Kubernetes - Dify Enterprise Docs | https://enterprise-docs.dify.ai/en-us/deployment/prerequisites/kubernetes
  • Dify Helm Chart - Dify Enterprise Docs | https://enterprise-docs.dify.ai/en-us/deployment/advanced-configuration/dify-helm-chart

Confirmed Information from Public Sources

  • License activation supports both online and offline modes
  • Offline activation requires switching licenseMode and using Cluster ID / Offline Code
  • A restart of dify-enterprise is required after activation or refresh for changes to take effect