Usage of pipeline variable resolver

[dave-csc]

Hello,

I'm trying to setup a variable resolver to decode the passwords encrypted in my configuration files (unfortunately it is still needed in some cases).

So I set up this pipeline: _res-decrypt-pwd.hpl.txt

And then setup a variable resolver with the following configuration:

• Name: pwd
• Type of variable resolver: Pipeline variable resolver
• Run configuration to use: local
• Variable name to contain the expression: PWD_ENCR
• Name of the output transform: Dummy output

I would expect to use the syntax #{pwd:MY_PASSWORD:d} to get the decrypted ${MY_PASSWORD} variable in a test pipeline, but I'm getting no results (an empty string): what am I doing wrong?

Thanks for your support... :)

[hansva]

Your resolver pipeline has a small issue.
The UDJC function should be org.apache.hop.core.encryption.Encr.decryptPasswordOptionallyEncrypted(e)

Also the second part "MY_PASSWORD" is a value if that needs to be a variable your expression should be #{pwd:${MY_PASSWORD}:d}

[hansva]

I also added a sample to the project: #6036

[dave-csc]

Thanks for the tips, I fixed the errors and it works! 😄

[dave-csc]

Hurraying too early... Unfortunately, there are still issues with the Copy/Move files actions to sFTP.

I tried to use the fixed variable resolver, but the password is not encoded correctly in the URL, the result displayed in the logs is something like: sftp://user:#{pwd:Encrypted 2be98a...:<password>@host/path (the full encrypted password is shown, <password> is shown as is and it's not a placeholder)

😢

[hansva]

If it's messed up with a get variables, you will have to take a look at why. I am guessing your ${DATAWEB_PWD} variable is incorrect then

[dave-csc]

The password is actually correctly resolved, when I use the variable resolver alone (i.e. #{pwd:${DATAWEB_PWD}:d} is resolved with the correct password). The things mess up when the same resolver is placed among other variables...

[hansva]

I'm not sure how to help you further.
You will have to simplify and see when it starts breaking.
I took over your exact example, and it seems to be working fine here...

Get variables:

[dave-csc]

Back here with some news: it turned out that's a (probably undetected) bug in version 2.15 that I was using yesterday.

After upgrading to 2.16, the long variable string is resolved correctly, password included!

(should I file a bug anyway with the auto-solution "upgrade to 2.16", just for the record?)

[hansva]

I wouldn't bother @dave-csc, it's written here... if people use Google search or an LLM they will probably find this discussion and resolution. Glad that you found the solution