yuqi1129 opened a new issue, #14638: URL: https://github.com/apache/gravitino/issues/14638
### Version main branch ### Describe what's wrong Catalog-level credentials are authorized as metadata reads, so a principal with USE_CATALOG can recover the source account's password and bypass table-level grants. JDBC URL passwords bypass key-based property masking and appear in catalog responses and class-loader diagnostics. Unsupported credential object types also return an internal error instead of a client error. ### Error message and/or stacktrace Credential responses expose plaintext login information; unsupported types return 500. ### How to reproduce 1. With authorization enabled, grant a user only USE_CATALOG and request catalog credentials. The configured source password is returned. 2. Configure a JDBC URL with a password parameter; load the catalog and inspect its returned properties and class-loader log. 3. Request credentials for a schema or table. The response is 500; provider errors can identify an empty object name. ### Additional context Catalog credential users must receive the explicit secret privileges. The returned credentials still carry the entire source account's permissions. Existing catalog configurations with URL credentials must be migrated to credential properties/secret references; loading or using them can fail until migration. URL masking is defensive protection for legacy properties that reach the read path. No new privilege, dependency, or store migration is introduced. -- 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]
