Hello everyone,
I want to encrypt the component node so that no one else can see the workflow inside the component node, how do I do this?
Thank you in advance.
Do you have a KNIME Server Large subscription?
If you do, get in contact with your partner manager or support@knime.com directly. They need to give you some codes.
To use the feature you need to add “-Dknime.showaction.metanodelock=true” to your knime.ini.
3 Likes
@ArjenEX
Thank you for your reply.
I don’t have a KNIME Server Large subscription. Is there another way?
As far as I know there is not. It’s a selling point for the server so it’s not very likely either but perhaps someone from KNIME can give the final confirmation.
@ArjenEX
Is there any way to hide this password? My main purpose is not to let anyone else know the password of the DB
If you right click on the workflow you can set credentials there
br
Could you tell me where can set credentials? I want to hide the password without affecting the normal use of the component node.
Thank you in- advance.
Right click on the workflow name in the KNIME explorer window on the left side
1 Like
But I still don’t understand how to use it, I set the password and open the display “no set”.
How do I use it?
Thank you so much!
I have used a String Widget as an insecure version of a password to keep novice users out of certain settings in components. You can easily find the matching password in the Java Snippet, but if the component is shared and uploaded without data then it makes it prohibitively difficult for a novice. Making a minor change to a shared component can also clear a passwords everywhere after users update shared components.
This approach works better with “interactive view” based setting controls because of the refresh button. You can either hide settings via flow variable or bypass areas via if switches.
Not a true secure solution, but it can avoid some novice user problems.
Hi @iCFO
Thank you for your reply. But I don’t get your point, I just want to share Component node and hide the password, but the Component node can use for other people.
My bad. I missed the post about hiding the password of your DB.
My method only works as a “user deterrent” by limiting component setting access by novice users.
I don’t believe that there is a strong encryption solution to your problem if an advanced user really wants that password. You could help hide it from a group of trusted users with a few tricks like placing components within components and not showing credentials settings in config or interactive views of the component. Sorry, but I don’t think there is really a full solution to this outside of KNIME Sever Large as @ArjenEX said.