JMP licenses
JMP is licensed on a named-user basis. That is, our contracts allow named individuals to use JMP. We don’t license JMP for use on an individual machine, which would allow anyone with access to that machine to use JMP.
Up until JMP 18, our software licensing schemes have not supported this distinction. Using license files (JMP.PER/SID) or serial numbers assured that, at a minimum, JMP is licensed, but it didn’t limit usage solely to authorized users.
Additionally having multiple software licensing methods (license files/serial numbers) meant that we had different executable images for each. That situation caused significant confusion if a user expected to use a .PER file and had the activation version installed.
Starting with JMP 18, we will have one user authorization scheme that will support our contractual license and give one executable image per product that is usable regardless of the business transaction that gave a user access to JMP. So, whether it's annual license, subscription/store, trial, or student, all will have the same mechanism for authorizing users, resulting in one experience for all users.
When JMP 18 is launched, it will prompt users to log in with their My JMP ID. My JMP will look to see if that user is authorized to use JMP, what the expiration date is, and then start up.
Under this new protocol, all transaction methods will be connected to Salesforce to store the license details and the users authorized to use JMP under those licenses.
Adding authorized users
Software administrators for both subscription and annual licenses will use My JMP to grant (or remove) authorizations to individuals, using their email address as the identifier.
When an administrator logs into My JMP they will find their licensed software.
In the list of licensed software, JMP 18 shows a Manage option.
Authorizing JMP when first launched
Here's a prototype of what authorization looks like when JMP is launched.
Double click on the JMP icon to launch JMP and a prompt app a dialog appears asking for login to My JMP.
Login to My JMP is done with an email verification code.
This is the email with the verification code.
Enter the verification code.
Congratulations. You're authorized to run JMP.
Frequently asked questions
Q: What if an administrator has tens, hundreds, or even thousands of users to authorize?
A: My JMP will support uploading a .csv file of email addresses.
Q: If an email address is the identifier, what happens if a person changes email address?
A: Their administrator will have to de-authorize their old email address and grant a new authorization for the new address. We do not allow users to change their email address because we don’t know the reason for the change. For example, if an individual leaves their company, the license doesn’t move with them.
Q: We have some contracts that allow anyone at a company to use JMP. Do they have to tell us all their employees?
A: No, we will ask them to tell us the email domain(s) and will automatically grant a software authorization for anyone who logs into My JMP with an address with that domain(s).
Q: What about machines that can’t connect to the internet? How will users authorize JMP on those machines?
A: Users will be able to log into My JMP through a web browser and authorize those machines.
Q: How often will JMP check to ensure that the user is still authorized to use JMP?
A: Every time it is launched, JMP will silently check that the user who originally authorized that installation is still authorized. These silent checks are known as soft check-ins. Every so often, JMP will require a hard check-in, asking the user to log into My JMP to ensure they still have access to that email address.
Q: On how many machines will a user be allowed to run JMP?
A: We will not limit the number of machines a user can authorize on, but the more machines that a person authorizes on, the more often they’ll have to verify their log in to My JMP with a hard check-in. For example, if they authorize on three machines and then one more, when they return to the first of the original three, they’ll have to log back in with My JMP.
