Red Hat Summit Red Hat Summitサポートコンソール開発者トライアルの開始お問い合わせ

このコンテンツは選択した言語では利用できません。

Chapter 1. A

1.1. Access Operator
リンクのコピー

An optional operator that simplifies the sharing of Kafka connection information and credentials between namespaces. Connection details are stored centrally in a Secret resource.

1.2. Authentication
リンクのコピー

Defines how clients prove their identity to the Kafka cluster. Streams for Apache Kafka manages authentication as a client-server relationship:

  • Server-Side: The Kafka cluster’s listeners are configured to require a specific authentication type.

  • Client-Side: A client (a KafkaUser or a client-based Kafka component managed by Streams for Apache Kafka) must be configured to provide matching credentials.

    Listener authentication (Server-Side)
    Listener authentication is configured per listener in the spec.kafka.listeners array of the Kafka custom resource. Supported types include tls, scram-sha-512, and custom.
    Client authentication (Kafka user)
    For Kafka users, authentication is managed using the KafkaUser custom resource. Supported types are tls, tls-external (using an external CA), and scram-sha-512. Streams for Apache Kafka automatically creates the necessary Secret resources for the user.
    Client authentication (Kafka components)
    For Streams for Apache Kafka-managed components, authentication is managed in the custom resource of the component, such as KafkaConnect. Supported types include tls, scram-sha-256, scram-sha-512, plain, and custom.

For more information, see the following:

1.3. Authorization (cluster-wide)
リンクのコピー

Defines which actions an authenticated client is permitted to perform on Kafka resources, such as writing to or reading from a topic. Configuration involves setting a cluster-wide mechanism and then, if required, defining user-specific rules.

Cluster-wide authorization
This defines the overall mechanism used by the Kafka cluster to control client actions. It’s configured in the spec.kafka.authorization section of the Kafka custom resource. Supported types include simple (using the Kafka’s built-in authorizer) and custom (using custom authorizers).
User authorization (ACLs)
This defines specific Access Control Lists (ACLs) for a user, granting permissions to perform actions on Kafka resources. The ACLs are defined in the spec.authorization section of the KafkaUser custom resource. If using a custom authorization mechanism, user permissions are typically managed within the external authorization system and not through the KafkaUser resource.

For more information, see the following:

トップに戻る
Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

Red Hat ドキュメントについて

Red Hat をお使いのお客様が、信頼できるコンテンツが含まれている製品やサービスを活用することで、イノベーションを行い、目標を達成できるようにします。 最新の更新を見る.

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

Theme

© 2025 Red Hat