Skip to content

Do not make ANONYMOUS superuser when with none authentication #13142

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
scholzj wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −8
Open

Do not make ANONYMOUS superuser when with none authentication #13142

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions ...ator/src/main/java/io/strimzi/operator/cluster/model/KafkaBrokerConfigurationBuilder.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -550,10 +550,6 @@ public KafkaBrokerConfigurationBuilder withAuthorization(String clusterName, Kaf
superUsers.add(String.format("User:system:serviceaccount:%s:%s", reconciliation.namespace(), KafkaExporterResources.serviceAccountName(clusterName)));
superUsers.add(String.format("User:system:serviceaccount:%s:%s", reconciliation.namespace(), CruiseControlResources.serviceAccountName(clusterName)));
superUsers.add(String.format("User:system:serviceaccount:%s:%s", reconciliation.namespace(), KafkaResources.clusterOperatorServiceAccount(clusterName)));
} else {
// When authentication is disabled, all internal synchronization is using the ANONYMOUS user. In order
// to support authorization, we have to make this user a super-user.
superUsers.add("User:ANONYMOUS");
}

printSectionHeader("Authorization");
Expand Down
2 changes: 1 addition & 1 deletion .../src/test/java/io/strimzi/operator/cluster/model/KafkaBrokerConfigurationBuilderTest.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -424,7 +424,7 @@ public void testSimpleAuthorizationWithoutMtls() {

assertThat(configuration, isEquivalent("node.id=2",
"authorizer.class.name=org.apache.kafka.metadata.authorizer.StandardAuthorizer",
"super.users=User:ANONYMOUS;User:jakub;User:CN=kuba"));
"super.users=User:jakub;User:CN=kuba"));
}

@Test
Expand Down
6 changes: 3 additions & 3 deletions documentation/modules/security/con-internal-cluster-security.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,9 +69,10 @@ The supported combinations are:
* No encryption with service account authentication
* And no encryption with no authentication

WARNING: When the authentication type is `none` and Kafka authorization is configured, Strimzi automatically makes the `ANONYMOUS` user a super user so that internal components can operate.
This gives unrestricted access to any connection that Kafka identifies as `ANONYMOUS`, including connections through an unauthenticated client listener.
WARNING: When the authentication type is set to `none`, all internal connections between the Kafka cluster components are unauthenticated and use the `ANONYMOUS` principal.
Disable authentication only if other controls, such as network isolation or a service mesh, prevent unauthorized access.
If you want to enable Kafka authorization in such a cluster, you must configure the `ANONYMOUS` user as a super user to make the internal components operate correctly.
This gives unrestricted access to any connection that Kafka identifies as `ANONYMOUS`, including connections through an unauthenticated client listener.

== Default internal cluster security

Expand Down Expand Up @@ -145,7 +146,6 @@ The service account exists only while service account authentication is enabled.
|===

When Kafka authorization is configured, Strimzi adds these principals to the list of Kafka super users so that internal components can operate.
Unlike the `none` authentication type, the `ANONYMOUS` user is not made a super user.

Service account authentication has the following requirements:

Expand Down
Loading