LuciferYang commented on issue #11307:
URL: https://github.com/apache/gravitino/issues/11307#issuecomment-6576670850
I wrote a design for this issue: #14539. It takes a different shape from the
decision API sketched above.
A trusted service sends the end user in an `X-Gravitino-Proxy-User` header,
and Gravitino checks it against server-side proxy rules, as Hadoop proxy users
do. A `POST /api/metalakes/{metalake}/authorize` endpoint answers only allow or
deny: the connector's metadata calls would still run as the service account, so
ownership and audit stay wrong, and Lance REST (#13090) is not covered. The
doc's Solution Investigations section compares the two.
@fzhsbc, I'd like to hear your view before implementation. cc @diqiu50 for
the Trino connector changes, and @yuqi1129 since #13092 covers the same need
for Lance REST.
--
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]
