niumy0701 commented on issue #17813: URL: https://github.com/apache/dolphinscheduler/issues/17813#issuecomment-3713690907
> Having a separate button just for changing passwords isn't very good, it's hard to check the datasource other param. One effective approach I can think of is to return an empty password field each time, meaning the interface never returns the password. Whenever the data source is updated, the password must be re-entered. hiļ¼one issue is that when a password is entered once, it can be difficult to distinguish whether the user actually intends to change the password or if it was a misoperation; It is best to have a secondary confirmation for password modification to prevent accidental operations; So, is it better to distinguish password modification from other parameter modifications -- 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]
