singhpk234 commented on PR #13225: URL: https://github.com/apache/iceberg/pull/13225#issuecomment-5588427725
> Or do we want to prohibit a client that advertises only storage vending, from using a locally configured KMS Its more on this lines, as if the client uses either only server side creds (storage + kms) or just client side creds (storage + kms)... this half an half is something i am looking for more cases .... > I also wonder about customer-managed Vault or cross-cloud KMS/storage use cases where a catalog vending KMS is not necessary / feasible, but I'm not too opinionated. cross cloud is possible right ? as kms can returns creds from different cloud, vault supports credential subscoping .... i think the case we would not be handle is the propreitary KMS (which doesn't support cred vending) .... do you have a use case for that ? I hear this case for using storage from server side creds and kms from client, i am told hive as precedence but i think hive is client side only. we need to have two different priviledge sets here client side to have kms:decrypt / kms:encrypt... but if we centrally manage this one has decrypt access to table only when one can read the table ... that would be better . I am just looking for uses case here ... also i am concerned of this being a default behaviour as well, if we were to do it may be we should add a feature flag with default false .... default being only client side creds (storage and kms) -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
