topic Re: How to use seeded encryption tool in Talend ESB Studio ? in Talend Studio

How to use seeded encryption tool in Talend ESB Studio ?

Loko — Sat, 16 Nov 2024 09:55:08 GMT

We need to encrypt passwords so that they're not human readable even in Talend ESB Studio. We tried this : https://help.talend.com//pages/viewpage.action?pageId=271836877

the feature tesb-encryptor-command is correctly installed in Karaf and we can run the command line to get encrypted texts, for instance we get ENC(dummy)

Then in a route we use this value "ENC(dummy)" in a string context parameter named "ftppassword" and use it as context.ftppassword to connect to an FTP server with a cFTP or cMessagingEndPoint, but it can't connect, the value seems not to be decrypted. Of course we gave a try and it works if we set the value directly the context parameter.

How are we supposed to use the encrypted texts in Talend Studio and routes ?

Loko

Re: How to use seeded encryption tool in Talend ESB Studio ?

Anonymous — Mon, 15 May 2017 08:09:21 GMT

Hi,

Could you please take a look at this new feature jira issue:https://jira.talendforge.org/browse/TESB-16366 to see if it is what you are looking for?

Best regards

Sabrina

Re: How to use seeded encryption tool in Talend ESB Studio ?

Anonymous — Mon, 15 May 2017 09:16:21 GMT

I have recently solved a problem like this using the following tutorials. First, this tutorial (http://blog.nanthrax.net/2014/10/encrypt-configadmin-properties-values-in-apache-karaf/) by Jean-Baptiste Onofre (the creator of Apache Karaf) shows you how to use Jasypt with Apache Karaf. This will also give you some Java which can be used in your Studio when debugging. Unfortunately you will need different code in your Studio because it doesn't run a version of the Karaf for testing (......when will this be in the Studio Talend?).

The second tutorial is by Ed Ost (another good guy to watch out for). He talks about using Property Placeholders. You may not need to use this, but it is in the domain of what you are talking about is quite useful (http://edwardost.github.io/cloud/platform/soa/2015/05/14/Working-with-Property-Placeholders-in-Talend-ESB/).

I hope this helps

Re: How to use seeded encryption tool in Talend ESB Studio ?

Loko — Mon, 15 May 2017 13:34:37 GMT

I have no idea about how to get the "results" of thoses JIRA issues

Re: How to use seeded encryption tool in Talend ESB Studio ?

Loko — Mon, 15 May 2017 13:35:28 GMT

Thank you Rhall

Having no answer from Talend I also went into self-enconding with JASypt and it works fine.

Re: How to use seeded encryption tool in Talend ESB Studio ?

vapukov — Mon, 15 May 2017 13:42:04 GMT

@rhall wrote:

Unfortunately you will need different code in your Studio because it doesn't run a version of the Karaf for testing (......when will this be in the Studio Talend?).

If I correct understand - this is exactly what was announced this weekend

1.1. General

The Studio now supports a local Talend Runtime in the Studio to test Routes and Data Service Jobs easily within the OSGI Runtime environment.

Re: How to use seeded encryption tool in Talend ESB Studio ?

Anonymous — Mon, 15 May 2017 13:44:55 GMT

Awesome news!! I requested this when I worked for Talend. I can't believe I missed this. Thanks for pointing this out @vapukov

Re: How to use seeded encryption tool in Talend ESB Studio ?

Loko — Mon, 15 May 2017 14:36:31 GMT

I'm not sure I understood correctly the latests 2 posts :

- what is the difference between the new Talend Studio Runtime and running our routes in the studio as we did until now ?

- Why should I need different code to run into Studio to developp and use Jasypt ? I could developp a "security" bean that uses this library and works fine both in Talend Studio and in Karaf (using sysenv as masterpassword)

Re: How to use seeded encryption tool in Talend ESB Studio ?

Anonymous — Mon, 15 May 2017 15:12:54 GMT

Talend Studio used to use a pseudo approximation of the actual Talend Runtime (Apache Karaf). This meant that if the route workd in the Studio you had to test it in a standalone runtime without easy access to debugging functionality. This is a pain. But they have now implemented the runtime into the Studio so that you can test exactly what you will be working with. This *should* remove the requirement for extra code in several situations to emulate the runtime.