danhuawang opened a new issue, #12580: URL: https://github.com/apache/gravitino/issues/12580
**Version**: main branch ## Describe what's wrong When editing a catalog on the UI page, secret/password fields (such as JDBC password or S3 secret key) are intentionally hidden by the API — the actual value is masked and not returned to the frontend. As a result, when a user tries to correct a wrong password by editing the catalog, the UI submits an empty or masked value, making it impossible to successfully update the credential. ## Error message and/or stacktrace No explicit error message. The catalog edit appears to succeed, but the password is not actually updated because the hidden field value is never sent correctly to the API. ## How to reproduce 1. Create a catalog with a password/secret property (e.g., a JDBC catalog with `jdbc.password`). 2. Use an incorrect password intentionally. 3. Go to the catalog edit page in the UI. 4. Try to update the password field with the correct value. 5. Save the catalog — the password field is not updated as expected because the API hides the original secret. ## Additional context The API masks secret properties for security reasons, which is correct behavior. However, the UI should still allow the user to input a new value and submit it, enabling the credential to be corrected on the edit page. -- 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]
