SaketaChalamchala opened a new pull request, #7081: URL: https://github.com/apache/ozone/pull/7081
## What changes were proposed in this pull request? Right now we cannot use a single client to read/write encrypted files to multiple Ozone clusters across trusted realms. This is resolved in HDFS. HDFS overrides the implementation of hadoop.fs.FileSystem.getServerDefaults() where Namenode returns it's default keyProviderUri to the client. The client then uses Namenodes keyProvider instead of it's local keyProvider to correctly read/write encrypted files. Proposed solution does the same in Ozone. OzoneManager returns it's server default configuration which includes it's keyProviderUri to the client. The client then uses the OM's keyProviderUri if available to get encryption keys before defaulting to it's local keyProvider. This enables the client to correctly encrypt/decrypt files from multiple Ozone clusters. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-11227 ## How was this patch tested? Manual test. Before the fix. <img width="1713" alt="HDDS-11227_before_fix" src="https://github.com/user-attachments/assets/cf32290a-9a16-408b-8a44-7957d952c948";> After the fix. <img width="1727" alt="HDDS-11227_after_fix" src="https://github.com/user-attachments/assets/b1a86537-222f-4e1d-81b0-e2f1dd5b9747";> Created a separate JIRA for a docker test: https://issues.apache.org/jira/browse/HDDS-11332 -- 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]
