-
-
Notifications
You must be signed in to change notification settings - Fork 656
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
java.nio.BufferUnderflowException when displaying topic data #1604
Comments
@BernhardBerbuir you seem to be facing the same issue as the one I faced recently. |
And the fact that you don't see anymore an error message like in 0.24.0 is due to a regression in error management that will be fixed with #1600 |
@BernhardBerbuir the 2 PR have been merged. Can you try again and tell us if everything is fine now ? |
@BernhardBerbuir reopen if not fixed |
I am using the
dev
version of AKHQ in order to use the feature "fine granular permissions" with OIDC. This bug does not occur with version0.24
anddefault-group: reader
.When I try to view the data of a topic, I see the following behaviour for some of the topics:
OR
Using the
/api/me
route I can verify that I have the following permissions (and some additional READ permissions):for topics whose name starts with my principal name (using the
pattern
"${PRINCIPAL_NAME}-.*" for both permissionsets).I have not been able to see what kind of topics are affected by the problem: the topic names consist only of lower-case letters, underscore, minus and digits. Some topics differ only in the suffix:
v1
instead ofv2
: one is displayed, the other is not.Version
0.24
of AKHQ showed the error message "Internal Server Error: Error for Consume with options {}" in the UI if the principal of AKHQ did not have permission to read data from the topic. But now the principal of AKHQ is a superuser, so missing Kafka ACLs can not be a problem.The text was updated successfully, but these errors were encountered: