"Whitelisting" means having IA sales inject your license details directly into the Edge platform license--no secondary key. You will have to:
Get IA sales to review your company and your module for suitability for Edge (basically, trusted to not provide any bypasses to the Edge platform limitations), and then
Have IA sales process licenses for you. Your clients will have to provide a list of their Edge license keys to update.
Sell enough to be annoying so they make an API for this (haven't yet).
What do you mean "no secondary keys"? Currently my drivers rely on keys that I transport using the IA licensing mechanism split up into 8 parameter entries for each key. Is that ok or is that considered bad? You don't need any "additional license file" it's all handled via the Ignition licensing mechanism.
For standard and cloud editions, 3rd parties create a 6-character (permanent) or 8-character (leased) license key and populate it with one or more module IDs. The module IDs can have key-value string pairs to trigger module optional behaviors. Such licenses are activated on a gateway using the normal licensing page and are independent of the actual platform license. They show up alongside the platform license as a secondary license.
Edge doesn't support secondary licenses. You have to inject the module ID and any parameters into the existing Edge 6- or 8-character platform license. 3rd parties cannot do this via API.
It sounds like you are using parameters to carry custom license information. That will have to be injected into existing Edge licenses.
Hmmm ... ok ... I think I'll have to investigate on how I can do that ... Because I'm integrating individual drivers in my ignition modules so the drivers themselves are protected and I'm only using the IA licensing as a vehicle for delivery.
In my system I have quite a number of bells and whistles, that I can't map to simply 6 or 8 characters.
Do you have any documentation pointers for me to chew through?
The 6- or 8-character keys are randomly generated by IA. They are associated with the details in IA's license servers.
Most modules don't take parameters. Just a maximum major version for which the license is valid. Each distinct installable module should have unique module ID (usually the outer java package name for the main code). Use string key-value pairs to enable premium options. (I only do this for my EtherNet/IP driver.)
Yeah ... I know ... I built my own system for generating the normal licenses that uses the IA API as I wasn't very happy with the Designer option and the Web-Version (It felt like none got me 100% of the way) ... but you mention, that you can set key-value pairs on a module Id to pass module specific settings ... that's what I'm using ... in the Designer frontend it's listed as "parameters". Is it ok to use these?
They are "driver-ads-0" to "driver-ads-8" ... I wouldn't expect any collisions But seems I picked the right mechanism. Now I would need to know how to pass these to the sales guys for integration into the licenses they generate.