You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting HOP_PASSWORD_ENCODER_PLUGIN=AES and adding HOP_AES_ENCODER_KEY=blablabla to hop-config.json passwords of new database connections are not encrypted as AES, password still starts with Encrypted. database connections is working correct. When creating an AES password with hop-encrypt and store in the databaseconnection json file, the authorization to the database server fails (it still expects an Encrypted password
HOP_PASSWORD_ENCODER_PLUGIN =AES is available in hop GUI:
Issue was also availble in 2.5
Issue Priority
Priority: 2
Issue Component
Component: Other
The text was updated successfully, but these errors were encountered:
Yeah I think this is a documentation error. The part saying or in the hop-config.json file., is incorrect.
The two way password encoder is already selected when the config file is sourced. This is why the startup scripts pick up these variables from the operating system.
Apache Hop version?
hop-client-2.6.0-20230912.091255
Java version?
11.0.20" 2023-07-18 LTS
Operating system
Windows
What happened?
Setting HOP_PASSWORD_ENCODER_PLUGIN=AES and adding HOP_AES_ENCODER_KEY=blablabla to hop-config.json passwords of new database connections are not encrypted as AES, password still starts with Encrypted. database connections is working correct. When creating an AES password with hop-encrypt and store in the databaseconnection json file, the authorization to the database server fails (it still expects an Encrypted password
HOP_PASSWORD_ENCODER_PLUGIN =AES is available in hop GUI:
![image](https://private-user-images.githubusercontent.com/1124891/268191213-b19d098e-5235-4a15-bb18-fe397d020774.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjEyMzcyODMsIm5iZiI6MTcyMTIzNjk4MywicGF0aCI6Ii8xMTI0ODkxLzI2ODE5MTIxMy1iMTlkMDk4ZS01MjM1LTRhMTUtYmIxOC1mZTM5N2QwMjA3NzQucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDcxNyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA3MTdUMTcyMzAzWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NjEyYWIwMDU3MjRkMWE5OGFiMzk5NjdjMTg1NGIxZWE3OGM2Mjc0MGFlYzk4OThmZjA1MDUyYjZkNGU5MzFmMCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.7i8y1BAqjd0i-mcOi_lpFweGpxS-xRatgeAE_vnnkP4)
Issue was also availble in 2.5
Issue Priority
Priority: 2
Issue Component
Component: Other
The text was updated successfully, but these errors were encountered: