LuciferYang opened a new issue, #14537: URL: https://github.com/apache/gravitino/issues/14537
### Describe the subtask Add the trusted proxy users design as `design-docs/gravitino-trusted-proxy.md` and review it with the community. It lets an authenticated service, such as the Trino connector or the standalone Lance REST server, act for an end user through an `X-Gravitino-Proxy-User` header that server-side proxy rules check, as Hadoop proxy users do. The doc covers: - Proxy rules: the authenticator, the verified identity, and the users, groups and client addresses a proxy may act for - Changes to `Authenticator`, `AuthenticationFilter` and `UserPrincipal` - `realUser` in audit logs and events - `withProxyUser` in the Java client - Trino connector `forwardUser` under `basic` and `kerberos`, and a proxy-caller mode for Lance REST - Catalog impersonation of proxied users on HMS and HDFS Prerequisite fixes are tracked separately: #14415, #14405 and #14406 (fixed). Open questions for the review: - Whether a rule's `hosts` should match the TCP peer address, as proposed, or the client address that `ClientAddressResolver` derives for `trustedProxies` (#14024) - Whether standalone servers should keep their own copy of the proxy rules, as proposed, or fetch them from the Gravitino server ### Parent issue #11307 -- 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]
