Not sure if it's already possible (didnt find it) but I would love to see a possibility to encrypt the morph projects. So you can only edit the projects when you have the correct password.
Hi @IGO,
What, in your opinion, would be the use case for such a feature? Can you please describe a scenario for it?
This way you could ensure that internal or external colleagues cannot adjust your projects.
@dgudkov, hello.
To second @IGO's request, I believe that the same situation that happens with me, applies to IGO.
we have our projects saved on a network directory to which multiple users have access to.
that said, currently multiple users are able to change the existing filters, the existing steps (adding or removing them), change the export file format (if any) at their discretion
that ultimately impacts the project execution and possibly its final goal, especially if the project execution is scheduled.
therefore, it would be useful for a project to be locked.
Hi!
It sounds like what you and @IGO are describing is more akin to 'digitally signing' morph projects. This means that instead of encrypting the projects (which would prevent them from being read without, say, a password), a signature is attached, so only the person with the private key can modify the project in a way that passes a signature test later. Is my guess correct?
I prefer that people can not read the projects. Only easymorph server, the commandline execturer or the person who has they key/password to read and edit them.
1 Like