[Bug][Seatunnel-web] Support encyrption of datasource data

[BilwaST]

Currently Datasource passwords are stored as it is in database and also is sent to seatunnel-engine in .profile file. All sensitive information like password should be encrypted. Also the API response should be encrypted for datasource password.

This patch handles the encryption of data using the encryption type available in seatunnel-engine. We can use base64 encryption type.

When we enable this encryption type, we need it configure it in job env like below:

env {
"shade.identifier" =base64
}

add shade.identifier to your env. you can refer to below doc for more understanding

https://seatunnel.apache.org/docs/2.3.2/connector-v2/Config-Encryption-Decryption/

[arshadmohammad]

I will review and test this PR in 1-2 days

[arshadmohammad]

password is not a mandatory field, it can be empty also, then this code will throw NPE. Encrypt only if passord is not empty.

[arshadmohammad]

How this feature works? I see encryption only, I do not see any decryption. How it will be able to connnect to databases, it will fail.
Can you please create datasource, create a job, execute the job and attache the snapshot here.

[BilwaST]

How this feature works? I see encryption only, I do not see any decryption. How it will be able to connnect to databases, it will fail. Can you please create datasource, create a job, execute the job and attache the snapshot here.

Thank you for reviewing. Decryption is done on the engine side. There is a ConfigShadeUtils which takes care of the decryption of password while connecting to the datasource. Sure, i can share the details.

[arshadmohammad]

Decryption is done on the engine side.
We are addressing two components in this context: the datasource and the generated job configuration.

1. In the Seatunnel-web, the datasource is used during job design via the UI. It's essential that it can establish a connection with the configured database. During this connection process, the encrypted password should be decrypted for successful connectivity.
2. The generated job configuration file needs to include the 'datasourceEncryptType'. In the env section, it should specify something like 'shade.identifier = "base64"'.

[BilwaST]

Hi @arshadmohammad
i have taken care of the scenarios you mentioned. Can you please review the updated patch