efajunk commented on PR #9678:
URL: https://github.com/apache/kafka/pull/9678#issuecomment-1512360596
Hello!
I'm not sure that the reason is still here, but we have exactly SASL
authentication and the delay "still" doesn't work.
Our Kafka version is 3.3. We see in logs that it's definitely applied, but
with no effect(
```
2023-04-17 14:58:36,322 INFO KafkaConfig values:
...
connection.failed.authentication.delay.ms = 1000
...
```
Log shows nonstop authorization attempts. One per 10 milliseconds (log e.g.
below). Errors rate for the same topic is kept at the 1-2k per minute.
```
2023-04-17 15:02:45,266 INFO Principal = User:same_user is Denied Operation
= Describe from host = x.x.x.x(same_ip) on resource = Topic:LITERAL:same_topic
for request = Metadata with resourceRefCount = 1 (kafka.authorizer.logger)
[handler-0]
2023-04-17 15:02:45,268 INFO Principal = User:same_user is Denied Operation
= Describe from host = x.x.x.x(same_ip) on resource = Topic:LITERAL:same_topic
for request = Metadata with resourceRefCount = 1 (kafka.authorizer.logger)
[handler-3]
2023-04-17 15:02:45,268 INFO Principal = User:same_user is Denied Operation
= Describe from host = x.x.x.x(same_ip) on resource = Topic:LITERAL:same_topic
for request = Metadata with resourceRefCount = 1 (kafka.authorizer.logger)
[handler-10]
2023-04-17 15:02:45,269 INFO Principal = User:same_user is Denied Operation
= Describe from host = x.x.x.x(same_ip) on resource = Topic:LITERAL:same_topic
for request = Metadata with resourceRefCount = 1 (kafka.authorizer.logger)
[handler-11]
```
Maybe there is still another config to make the delay work?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
