Hey Walchester,
There's a confluent community slack Workspace having a #security channel
where you can post your question. Also, have you filed a bug in AK JIRA
which can also help you get the traction of some of the community members
who have expertise in this area.
Thanks!
Sagar.
On Thu, Oct 1
Hello.
Is there something like a community page for Kafka where I can reach out to
the community where hopefully someone with a similar setup can help?
Thanks,
Chester
On Thu, Oct 12, 2023 at 10:48 AM Walchester Gaw
wrote:
> Hello.
>
> I am trying to implement Quorum TLS by following the inst
Hello.
I am trying to implement Quorum TLS by following the instructions in
https://zookeeper.apache.org/doc/r3.5.7/zookeeperAdmin.html#Quorum+TLS, but
I keep on encountering the following errors after doing the second rolling
restart where sslQuorum set to true.
- [2023-10-11 05:46:03,250] WA
rsion" in its details. This indicates which
version includes the fix.
In this case all subtasks are marked with "0.9.0.0", which is a future release.
So, no existing release includes the security patches, those will be part of
the next releas
ased authentication and the authorization
outlined here is now part of the latest kaffa release.
Does "Resolved" for one "subtask" means it has gone to a release ? Or all the
sub tasks need to be "REsolved" only then we can expect all the code changes in
the lates
king KAFKA-2162 a sub-task of this
ticket.
> Security for Kafka
> --
>
> Key: KAFKA-1682
> URL: https://issues.apache.org/jira/browse/KAFKA-1682
> Project: Kafka
> Issue Type: New Feature
> Compo
ttps://issues.apache.org/jira/browse/KAFKA-2162
> Security for Kafka
> --
>
> Key: KAFKA-1682
> URL: https://issues.apache.org/jira/browse/KAFKA-1682
> Project: Kafka
> Issue Type: New Feature
>
e is "Auditing". Is that information
up to date and if so, is there a ticket for it? All the other items seem to be
covered by the subtasks associated to this ticket.
> Security for Kafka
> --
>
> Key: KAFKA-1682
> URL: h
anks!
> Security for Kafka
> --
>
> Key: KAFKA-1682
> URL: https://issues.apache.org/jira/browse/KAFKA-1682
> Project: Kafka
> Issue Type: New Feature
> Components: security
>Affects Versions: 0
7;t think KAFKA-1927 should block KAFKA-1684 or KAFKA-1690.
1927 is application protocol changes its not going to affect the work done in
1684 and 1690 which is at socketchannel and network level.
> Security for Kafka
> --
>
> Key: KAFKA-1682
>
eeds to be done before KAFKA-1684 or
can be done in parallel?
> Security for Kafka
> --
>
> Key: KAFKA-1682
> URL: https://issues.apache.org/jira/browse/KAFKA-1682
> Project: Kafka
> Issue Type: New Feat
top of the network code in
o.a.k.c.n.
> Security for Kafka
> --
>
> Key: KAFKA-1682
> URL: https://issues.apache.org/jira/browse/KAFKA-1682
> Project: Kafka
> Issue Type: New Feature
> Compo
1688(Authorization), by [~parthrbhatt] , depending on KAFKA-1684 &
KAFKA-1686
> Security for Kafka
> --
>
> Key: KAFKA-1682
> URL: https://issues.apache.org/jira/browse/KAFKA-1682
> Project: Kafka
>
4 AM:
Also
5. KAFKA-1688(Authorization), by [~parth.brahmbhatt] , depending on KAFKA-1684
& KAFKA-1686
was (Author: sriharsha):
Also
5. KAFKA-1688(Authorization), by [~parthrbhatt] , depending on KAFKA-1684 &
KAFKA-1686
> Sec
1928.
4. KAFKA-1686 (SASL), by [~sriharsha], depending on KAFKA-1928.
> Security for Kafka
> --
>
> Key: KAFKA-1682
> URL: https://issues.apache.org/jira/browse/KAFKA-1682
> Project: Kafka
> Issue Type: New Feat
[
https://issues.apache.org/jira/browse/KAFKA-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Stein updated KAFKA-1682:
-
Component/s: security
> Security for Kafka
> --
>
> Key
/display/KAFKA/Security
> Security for Kafka
> --
>
> Key: KAFKA-1682
> URL: https://issues.apache.org/jira/browse/KAFKA-1682
> Project: Kafka
> Issue Type: New Feature
>Affects Versions: 0.9.0
>
Jay Kreps created KAFKA-1682:
Summary: Security for Kafka
Key: KAFKA-1682
URL: https://issues.apache.org/jira/browse/KAFKA-1682
Project: Kafka
Issue Type: New Feature
Affects Versions: 0.9.0
18 matches
Mail list logo