[HDDS-8718] Kerberos authentication not working for GrpcOmTransport

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.4.0
• Fix Version/s: 1.4.0
• Component/s: OM, S3
• Labels: pull-request-available
• Assignee: Ivan Zlenko
• Reporter: Ivan Zlenko
• Created: 29/May/23 17:47
• Updated: 16/Jun/23 08:14
• Resolved: 15/Jun/23 20:52

Description

In current implementation of GrpcOmTransport we do not passing information about Kerberos token between client and server. That's lead to broken GetSecret and RevokeSecret commands if we are switching to GrpcOmTransport. 

Right now ozone cli forced to use Hadoop3OmTransport so issues do not manifests itself at the moment. But implementation of HDDS-8050 currently blocked by this bug. 

To reproduce it one can simply need to change 

org.apache.hadoop.ozone.om.protocolPB.Hadoop3OmTransportFactory

 to 

org.apache.hadoop.ozone.om.protocolPB.GrpcOmTransport

 in 

hadoop-ozone/tools/src/main/resources/META-INF/services/org.apache.hadoop.ozone.om.protocolPB.OmTransportFactory

 . And execute following commands: 

ozone s3 getsecret
ozone s3 revokesecret

Issue Links

• blocks: HDDS-8050 Create HTTP endpoint to access S3 secret via Kerberos auth
• links to: GitHub Pull Request #4843