<commit_before>// Module included in the following assemblies:
//
// assembly-security.adoc

[id='certificate-authorities-{context}']
= Certificate Authorities

To support encryption, each {ProductName] component needs its own private keys and public key certificates.
All component certificates are signed by a Certificate Authority (CA) called the _cluster CA_.

Similarly, each Kafka client application connecting using TLS client authentication needs private keys and certificates.
The _clients CA_ is used to sign the certificates for the Kafka clients.

== CA certificates

Each CA has a self-signed public key certificate.

Kafka brokers are configured to trust certificates signed by either the clients CA or the cluster CA. Components to which clients do not need to connect, such as Zookeeper, only trust certificates signed by the cluster CA. Client applications that perform mutual TLS authentication have to trust the certificates signed by the cluster CA.

By default, {ProductName} generates and renews CA certificates automatically. You can configure the management of CA certificates in the `Kafka.spec.clusterCa` and `Kafka.spec.clientsCa` objects.
<commit_msg>fix typo in attribute (#1015)<commit_after>// Module included in the following assemblies:
//
// assembly-security.adoc

[id='certificate-authorities-{context}']
= Certificate Authorities

To support encryption, each {ProductName} component needs its own private keys and public key certificates.
All component certificates are signed by a Certificate Authority (CA) called the _cluster CA_.

Similarly, each Kafka client application connecting using TLS client authentication needs private keys and certificates.
The _clients CA_ is used to sign the certificates for the Kafka clients.

== CA certificates

Each CA has a self-signed public key certificate.

Kafka brokers are configured to trust certificates signed by either the clients CA or the cluster CA. Components to which clients do not need to connect, such as Zookeeper, only trust certificates signed by the cluster CA. Client applications that perform mutual TLS authentication have to trust the certificates signed by the cluster CA.

By default, {ProductName} generates and renews CA certificates automatically. You can configure the management of CA certificates in the `Kafka.spec.clusterCa` and `Kafka.spec.clientsCa` objects.

{'fraction_non_alphanumeric': 0.04675652906486942, 'fraction_numerical': 0.0016849199663016006, 'mean_word_length': 5.136950904392765, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '130126', 'n_tokens_mistral': 572, 'n_tokens_neox': 521, 'n_words': 314}