[jira] [Created] (HDDS-17149) Separate SecretKeyProtocol RPC identities from their internal Java interfaces

["Chia-Chuan Ho (Jira)" <ji...@apache.org>]

Chia-Chuan Ho created HDDS-17149:
------------------------------------

             Summary: Separate SecretKeyProtocol RPC identities from their internal Java interfaces
                 Key: HDDS-17149
                 URL: https://issues.apache.org/jira/browse/HDDS-17149
             Project: Apache Ozone
          Issue Type: Sub-task
            Reporter: Chia-Chuan Ho
            Assignee: Chia-Chuan Ho


Follow-up to HDDS-16246, applying the approach established in HDDS-16247.

The SecretKeyProtocol family combines internal Java service contracts with role-specific RPC identities. The actual Hadoop RPC protocols are exposed through SecretKeyProtocolDatanodePB, SecretKeyProtocolOmPB, and SecretKeyProtocolScmPB, backed by SCMSecretKeyProtocolService.

Move the shared Java methods to internal interfaces, preserving the distinction between shared key-retrieval operations and the SCM-specific checkAndRotate operation.

Retain the existing fully qualified names of SecretKeyProtocolDatanode, SecretKeyProtocolOm, and SecretKeyProtocolScm as empty RPC identity classes so that their protocol names and service-authorization ACL mappings remain unchanged.

Update implementations, callers, translators, and proxy providers to use the internal interfaces. Preserve existing behavior, PB interfaces, protocol versions, role-specific Kerberos metadata, and Protobuf definitions.

Verify PB metadata, authentication and authorization for each service role, key retrieval and rotation, HA failover, and client/server compatibility using existing test coverage where applicable.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org