Red Hat Summit 红帽全球峰会支持控制台（Console）开发人员开始试用联系人

此内容没有您所选择的语言版本。

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

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务，以及可以信赖的内容，帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情，请参阅红帽博客.

關於紅帽

我们提供强化的解决方案，使企业能够更轻松地跨平台和环境（从核心数据中心到网络边缘）工作。

Theme

© 2025 Red Hat