[KAFKA-10099] Kerberos authentication sets java authrizedId to authenticationId not autherizationId

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.3.0
• Component/s: security
• Assignee: Unassigned
• Reporter: Francois Fernando
• Created: 04/Jun/20 02:13
• Updated: 04/Jun/20 03:28

Description

Following authentication code in kafka still puzzles me (Lines 67-74: https://github.com/apache/kafka/blob/3cdc78e6bb1f83973a14ce1550fe3874f7348b05/clients/src/main/java/org/apache/kafka/common/security/authenticator/SaslServerCallbackHandler.java).

private void handleAuthorizeCallback(AuthorizeCallback ac) {
  String authenticationID = ac.getAuthenticationID();
  String authorizationID = ac.getAuthorizationID();

  LOG.info("Successfully authenticated client: authenticationID={}; authorizationID={}.",
{{ authenticationID, authorizationID);}}

  ac.setAuthorized(true);
  ac.setAuthorizedID(authenticationID);
}

In a kafka cluster secured with Kerberos, using a kafka keytab with principal like `sys_read/[e-mail]` results in:

authenticationID = [e-mail];
authorizationID = sys_read/[e-mail]

Last line of above method sets the authorizedID to authenticationID not authorizationID. From my understanding of java security, the principal will become what's set in AuthorizedID.

This means the ACL definitions can't use the full principal string as the principal as authorizer will never see it. This leads to a confusing bug in spark structured streaming where the ACL has to be added without the host part of the principal.