Unable to use HdinsightKafka REST proxy API after authenticating with access token.

AwesomePaul 20 Reputation points
2024-07-10T12:25:43.3633333+00:00

Hello Team,

I'm having issues connecting to HdInsight kafka using REST proxy endpoint. I followed the steps here (https://video2.skills-academy.com/en-us/azure/hdinsight/kafka/rest-proxy), and was able to get token and authenticate the endpoint.

However, whenever I try to get topics, or brokers it returns an empty array, with 200 response. I also attempted to create a topic and got the following error {\n "code" : 500,\n "reason" : "Internal Server Error",\n "detail" : "",\n "clientIP" : "/41.217.63.247:58318"\n}

Please, how do i go about resolving this issue ?

Thanks.

Azure HDInsight
Azure HDInsight
An Azure managed cluster service for open-source analytics.
210 questions
0 comments No comments
{count} votes

Accepted answer
  1. PRADEEPCHEEKATLA-MSFT 88,636 Reputation points Microsoft Employee
    2024-07-11T01:49:42.3933333+00:00

    @AwesomePaul - Thanks for the question and using MS Q&A platform.

    First, it's important to note that the REST proxy endpoint requires an OAuth token for authentication. You mentioned that you were able to authenticate the endpoint, but it's possible that there was an issue with the token or the authentication process.

    To troubleshoot this issue, I would recommend checking the following:

    • Make sure that the OAuth token you're using is valid and has the necessary permissions to access the Kafka cluster. You can check this by decoding the token and verifying the claims.
    • Check the REST API reference to ensure that you're using the correct endpoints and parameters for the operations you're trying to perform. You can find the reference here: https://docs.microsoft.com/rest/api/hdinsight-kafka-rest-proxy/
    • Verify that the Kafka cluster is running and accessible. You can do this by using a Kafka client to connect to the cluster directly.

    If you've checked these items and are still having issues, it's possible that there's an issue with the Kafka cluster or the REST proxy endpoint. In this case, I would recommend opening a support ticket for further assistance.

    Hope this helps. Do let us know if you any further queries.


    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.