Skip to content

Releases: Aiven-Open/auth-for-apache-kafka

v4.0.0

08 Nov 13:31

Choose a tag to compare

  • Removed AivenAclAuthorizer and AivenKafkaPrincipalBuilder which are replaced by AivenAclAuthorizerV2 and AivenKafkaPrincipalBuilderV2 respectively. The deleted classes are not Kafka 3+ compatible, their replacements are Kafka 2.4+ compatible. The V2 suffix is kept despite the major version bump, to ensure that code that still references the old classes fails with a class not found error.

v3.6.1

08 Nov 09:12

Choose a tag to compare

  • Fixed the file descriptor leak (e.g. inotify instance leak) in AivenAclAuthorizerV2

v3.6.0

23 Sep 11:49

Choose a tag to compare

  • AivenAclAuthorizerV2 dependence on the old API was removed. Now AivenAclAuthorizer is the only class directly depending on the old API.
  • AivenKafkaPrincipalBuilderV2 was added, which supports KafkaPrincipalSerde interface.

v3.5.0

17 Sep 06:41

Choose a tag to compare

  • AivenAclAuthorizer is now deprecated.
  • AivenAclAuthorizerV2 is switched to the new Kafka auth API.

v3.4.0

11 Aug 09:15

Choose a tag to compare

Release notes:

  • Added new implementation of authorizer AivenAclAuthorizerV2 as a replacement for AivenAclAuthorizer that has a concurrency-related issue.

v3.3.0

05 Jul 10:25

Choose a tag to compare

A new property aggregation_type was added for the Kafka auth audit.
This property is applicable only for the UserOperationsActivityAuditor auditor type and can have two values:

  • user - records groupped by user;
  • user_and_ip - records groupped by user and IP address.

The default value is user_and_ip

v3.2.1

18 Mar 10:12

Choose a tag to compare

Add possibility to build fat jar

v3.2.0

18 Mar 09:58

Choose a tag to compare

Switched to JDK11

3.1.2

07 Jul 07:59

Choose a tag to compare

Add new flag:

  • aiven.acl.authorizer.log.denials - turns off authorization denials logging on Kafka brokers, default values is false

3.1.1

15 Apr 09:55

Choose a tag to compare

This release contains fix for the bug with authorization.
It strongly recommended do not use release 3.1.0