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

[Azure Event Hubs for Kafka] Unable to get topic configs if one topic does not have sufficient permissions #4300

Open
4 tasks done
azotcsit opened this issue Oct 20, 2023 · 1 comment · May be fixed by #4301
Open
4 tasks done
Labels
status/triage Issues pending maintainers triage type/bug Something isn't working

Comments

@azotcsit
Copy link

Issue submitter TODO list

  • I've looked up my issue in FAQ
  • I've searched for an already existing issues here
  • I've tried running master-labeled docker image and the issue still persists there
  • I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

Kafka UI fails to display topics if its credentials have access to a subset of Azure Event Hubs existing in the same namespace.

Basically the use case is like this:
There are multiple Azure Event Hubs in the same namespace. There are used by different teams. Every team has access to a subset of Event Hubs (topics) and uses corresponding credentials. Everything works perfectly fine except Kafka UI. It displays no topics.

Expected behavior

Kafka UI should display topics it has access to.

Your installation details

App version:
0.7.1
Configuration:

kafka:
  clusters:
    - name: Azure Event Hubs
      bootstrapServers: <REMOVED>.servicebus.windows.net:9093
      properties:
        security.protocol: SASL_SSL
        sasl.mechanism: PLAIN
        sasl.jaas.config: org.apache.kafka.common.security.plain.PlainLoginModule required username="$ConnectionString" password="Endpoint=sb://<REMOVED>.servicebus.windows.net/;SharedAccessKeyName=<REMOVED>;SharedAccessKey=<REMOVED>";

Steps to reproduce

There are no specific steps to reproduce, just start the application and make sure no topics are displayed.

Screenshots

No response

Logs

There is the following exception in logs:

2023-10-20 00:19:44,596 ERROR [parallel-13] c.p.k.u.s.StatisticsService: Failed to collect cluster local info
org.apache.kafka.common.errors.UnknownServerException: ExceptionId: 31745dbc-e75e-4c66-91a6-9f2eae1115e4-Microsoft.Azure.Kafka.KafkaException: Unauthorized access to topic 'ltd-event-enrichment'
   at Microsoft.Cloud.ServiceBus.Messaging.Kafka.KafkaAuthHandler.<AuthorizeAsync>d__16.MoveNext() in X:\bt\1247678\repo\src\product\Service\Messaging\Microsoft.Cloud.ServiceBus.Messaging\Kafka\KafkaAuthHandler.cs:line 221
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Cloud.ServiceBus.Messaging.Kafka.KafkaRequestHandler.<GetEndpointAsync>d__29.MoveNext() in X:\bt\1247678\repo\src\product\Service\Messaging\Microsoft.Cloud.ServiceBus.Messaging\Kafka\KafkaRequestHandler.cs:line 99
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Cloud.ServiceBus.Messaging.Kafka.KafkaRequestHandler.<GetFragmentEntityInformationAsync>d__35.MoveNext() in X:\bt\1247678\repo\src\product\Service\Messaging\Microsoft.Cloud.ServiceBus.Messaging\Kafka\KafkaRequestHandler.cs:line 393
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.Cloud.ServiceBus.Messaging.Kafka.DescribeConfigsHandler.<HandleAsync>d__0.MoveNext() in X:\bt\1247678\repo\src\product\Service\Messaging\Microsoft.Cloud.ServiceBus.Messaging\Kafka\DescribeConfigsHandler.cs:line 62

Additional context

No response

@azotcsit azotcsit added status/triage Issues pending maintainers triage type/bug Something isn't working labels Oct 20, 2023
@github-actions
Copy link

Hello there azotcsit! 👋

Thank you and congratulations 🎉 for opening your very first issue in this project! 💖

In case you want to claim this issue, please comment down below! We will try to get back to you as soon as we can. 👀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/triage Issues pending maintainers triage type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant