With the new feature of project inheritable in Ignition 8, we would like to be able to lock access to the Project inherited by other project.
Project Standard (locked - can’t be open or visible) => ressources are locked
- Project Custom => can be modified and edited by end user
Is there some plan for such a OEM lock feature in Ignition 8 ?
Maybe. It comes up once in a while, but it doesn’t seem to be real high priority.
And I’m always arguing against it because it’s just obfuscation sold as security. It’s impossible to actually prevent a determined or intelligent adversary from recovering the resources and being able to copy and modify them. If Ignition can decrypt/read/access the resources then so can they.
Kevin, I want to revive this. As an OEM, we constantly are asked to open up our software so our customers can make modifications. I would not mind this except some of our "secret sauce" is in the project. If we could lock the inherited project we wouldn't end up losing customers to other platforms when we refuse to unlock our code.
Don't hold your breath.
If you really need to protect your "secret sauce", it needs to be in a java add-on module.