njnu-seafish opened a new issue, #17813: URL: https://github.com/apache/dolphinscheduler/issues/17813
### Search before asking - [x] I had searched in the [DSIP](https://github.com/apache/dolphinscheduler/issues/14102) and found no similar DSIP. ### Motivation When editing a data source, the password field returned by the backend is masked as "*****". If the user does not change the password, the backend treats this mask as the plaintext password entered by the user during testing and saving. The current implementation is prone to accidentally overwriting the data source's password. ### Design Detail Option 1: Add connectivity validation when saving the data source. Option 2: If the user has not modified the password (i.e., the frontend sends the masked value "*****"), the backend should not treat this mask as the actual password provided by the user. Option 3: When editing a data source, the password field should be left blank instead of displaying a mask (e.g., "*****"). Option 4: Separate the password modification action from the modification of other data source information. ### Compatibility, Deprecation, and Migration Plan _No response_ ### Test Plan _No response_ ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
