If you do not encrypt your authentication password, it remains stored and visible in the configuration file (shared connection) or in the graph itself (internal connection). Thus, the authentication password could be seen in one of these two locations.

Of course, this would not present any problem if you were the only one who had access to your graph or computer. But if this is not the case then you would be wise to encrypt your password since it provides access to your database.

So, in case you want or need to give someone any of your graphs, you likely rather not give him or her the authentication password. This is the reason why it is important to encrypt your authentication password. Without doing so, you would be at great risk of some intrusion actions or other damage from whoever who could get this authentication password.

Thus, it is important and possible that you give him or her the graph with the authentication password encrypted. This way, no person would be able to receive and/or produce the messages without your permission.

In order to hide your authentication password, you must select Encrypt password by checking the checkbox in the Edit JMS connection wizard, typing a new (encrypting) password to encrypt the original (now encrypted) authentication password and clicking the Finish button.

You will no longer be able to run the graph by choosing Run as → CloudConnect graph if you encrypt the password. Instead, to run the graph, you must use the Run Configurations wizard. There, in the Main tab, you must type or find by browsing the name of the project, its graph name, its parameter file and, most importantly, type the encrypting password in the Password text area. The authentication password cannot be read now, it has been already encrypted and cannot be seen either in the configuration file or the graph.

If you should want to return to your authentication password, you can do it by typing the encrypting password into the JMS connection wizard and clicking Finish.