fzhsbc opened a new pull request, #11309: URL: https://github.com/apache/gravitino/pull/11309
### What changes were proposed in this pull request? Add Trino connector authorization documentation that explains identity boundaries between the Trino end user, Trino service identity, and Gravitino user. The page documents session user forwarding, BI/JDBC/ODBC considerations, Trino access-control integration guidance, and a typical mapping from Trino operations to Gravitino RBAC privileges. The Trino connector index is also updated to link both Authentication and Authorization pages. ### Why are the changes needed? In multi-user Trino deployments, connector authentication to Gravitino is not the same as query authorization. BI/JDBC/ODBC clients may not always be able to forward a Gravitino-audience OAuth token, so deployments need clear guidance on how to avoid trusting client-supplied user names and how to bind Trino's authenticated session identity to Gravitino policies. Related to #11307. ### Does this PR introduce _any_ user-facing change? Yes. It adds documentation only. No runtime behavior changes. ### How was this patch tested? - Ran `git diff --check`. - Reviewed the generated Markdown content and Trino connector index changes locally. -- 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]
