What inspired this wish list request?
This request is inspired by the cumulative burden of teams licensing JMP v19 on systems that are intentionally air-gapped, i.e. not connected to the internet. In the current offline activation workflow, JMP generates a ~70 character request code that is entered on the JMP website, which then returns a 700+ character response code that is hundreds of characters long and must be typed back into the offline machine. In highly restricted or air-gapped environments, transferring files onto a system can be extremely difficult or prohibited, making manual entry the only option. Typing long character codes is slow, error-prone, and often leads to failed activations even when the license itself is valid.
What is the improvement you would like to see?
I would like to see an option for simplified offline activation entry. Instead of requiring the full response code to be manually typed, JMP could accept a short verification code derived from the response (e.g. 6 characters from a cryptographic hash), while still validating the full response internally. To maintain security, JMP could limit the number of failed attempts and require contacting JMP support after repeated failures. This approach would preserve the existing licensing model while making the human interaction portion of the process far more manageable.
Why is this idea important?
This change would significantly improve usability for customers working in regulated or other environments where offline installation is common. It would reduce transcription errors, activation failures, and time spent retrying license entries, while also lowering support burden. Overall, it would make JMP more practical and user-friendly in real-world offline deployment scenarios without meaningfully weakening security.
... View more