Authenticate to open source Apache Kafka API

Clients can connect to Google Cloud Managed Service for Apache Kafka clusters by using the open source Apache Kafka API. Applications must communicate with Managed Service for Apache Kafka over TLS by using the credentials of an authorized Google Cloud service account. Managed Service for Apache Kafka clusters support only TLS connections; plaintext communication is not supported. Managed Service for Apache Kafka manages the certificate logic generation and maintenance.

Managed Service for Apache Kafka supports authentication over OAUTHBEARER and SASL to convey Google Cloud principal identifiers. The Google Cloud principal is used within Managed Service for Apache Kafka as the client principal. An example of a Google Cloud principal is a service account email.

Learn more about the following:

• Service accounts overview

• Authenticate to the Managed Kafka API

• Principal identifiers

Grant the Managed Kafka client role to the service account

You must grant the roles/managedkafka.client role on the project containing the cluster to the service account that you are going to use to connect to the cluster.

The Managed Kafka client role includes the permission managedkafka.clusters.connect required for all connections. To grant the Managed Kafka client role to the service account, follow these steps:

Configure the Kafka client for authenticating to Google Cloud

You can authenticate Kafka clients to Google Cloud by using one of the following mechanisms:

OAUTHBEARER (Recommended): This mechanism requires using Application Default Credentials (ADC). ADC is a strategy used by the authentication libraries to automatically find credentials based on the application environment. For more information about where ADC looks for credentials and in what order, see How Application Default Credentials works.

SASL_PLAIN: This mechanism requires using a username and password that are derived from the service account keys.

In general, OAUTHBEARER is the recommended option. However, SASL_PLAIN might be a more convenient mechanism for testing.

OAuthBearer authentication

For information about how to authenticate to the open source Kafka API, see the documentation at GitHub.

SASL_PLAIN authentication

This method is applicable to all Kafka clients.

Service account keys are a security risk if not managed correctly. You are responsible for the security of the private key and for other operations described by Best practices for managing service account keys. If you are prevented from creating a service account key, service account key creation might be disabled for your organization. For more information, see Managing secure-by-default organization resources.

1. Download a service account key JSON file for the service account that you intend to use for your client.

2. Encode the service account file by using base64-encode to use as your authentication string. Assume the filename as my_service_account.json.

   On Linux or macOS systems, use the base64 command (often installed by default) as follows:

   base64 < my_service_account.json > password.txt
   

   This command performs the following actions:

   • base64 < my_service_account.json: Reads the contents of the file my_service_account.json.

   • Encodes the file's contents using base64 encoding. Base64 encoding is a way to represent binary data (such as JSON data in your service account file) as ASCII text. This is often used for transmitting data over channels that are designed for text.

   • > password.txt: Redirects the output of the base64 command (the base64 encoded version of your service account file) into a new file named password.txt.

3. You can use the contents of the password file for authentication with the following parameters.

   security.protocol=SASL_SSL
   sasl.mechanism=PLAIN
   sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required \
   username="service account email" \
   password="contents of base64 encoded password file";
   
   

When authenticating incoming connections to the cluster, Managed Service for Apache Kafka checks the following:

1. The provided service account principal has the permission managedkafka.clusters.connect (included in roles/managedkafka.client) on the cluster.

2. The provided username matches the service account whose key is used in the password.

Troubleshoot authentication errors

If a Managed Service for Apache Kafka client cannot authenticate to Managed Service for Apache Kafka, you see an error message similar to the following:

Exception in thread "main" java.util.concurrent.ExecutionException:
org.apache.kafka.common.errors.SaslAuthenticationException:
Authentication failed: Invalid username or password

To resolve the issue, check for the following causes:

• The password is malformed, and doesn't represent a valid service account key JSON blob when base64 decoded.

• The principal in the service account key doesn't have IAM permissions on the cluster.

• The provided username doesn't match the credential's principal.

What's next

• IAM roles and permissions versus Kafka ACLs.

• Authenticate to Managed Kafka API.