Skip to content
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.

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

[ksqlDB] when using ACLs configure all internal topics with ALL permissions for the ksql server user #433

Merged
merged 7 commits into from
Dec 30, 2021
Original file line number Diff line number Diff line change
Expand Up @@ -19,8 +19,10 @@ public String getOwner() {
return owner;
}

public String commandTopic() {
return String.format("_confluent-ksql-%s_command_topic", ksqlDbId);
public String commandTopic() { return String.format("_confluent-ksql-%s_command_topic", ksqlDbId); }

public String internalTopics() {
solita-juusoma marked this conversation as resolved.
Show resolved Hide resolved
return String.format("_confluent-ksql-%s", ksqlDbId);
}

public String processingLogTopic() {
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -355,7 +355,7 @@ private Stream<AclBinding> ksqlServerStream(KsqlServerInstance ksqlServer) {

bindings.add(
buildTopicLevelAcl(
principal, ksqlServer.commandTopic(), PatternType.LITERAL, AclOperation.ALL));
principal, ksqlServer.internalTopics(), PatternType.PREFIXED, AclOperation.ALL));
bindings.add(
buildTopicLevelAcl(
principal, ksqlServer.processingLogTopic(), PatternType.LITERAL, AclOperation.ALL));
Expand Down