Kafka topic using OAuth2 authentication

Hi jfnumainville ! Thank you for the question. In theory, this should work. While there's no detailed instruction, I hope this document can be of some help!

https://support.smartbear.com/readyapi/docs/testing/kafka/auth.html#manual

I also recommend looking into Kafka documentation and searching there for parameters needed for OAuth 2.0.

Hi jfnumainville , thank you for your feature request! We are working on adding your feature (OAuth2.0 support for Kafka) to ReadyAPI. We plan to include it in one of the next app versions.

Can you please let us know which Get Access Token flows you like to use (more often) to get the access token from the authorisation server? 

We have prioritised these types, starting with the most important one (based on most used flows and based on the use case):  Authorization Code grant, Implicit Grant, Resource Owner Password Credentials Grant, Client Credentials Grant and JWT Profile Authorization Grants (please see the attached image for that).

Thank you,

Daniel, SmartBear ReadyAPI team

Hi J-F,

Thanks for your quick response ! that is very useful for us 🙂

Can you also please let us know what version of Kafka & Kafka clients are you using ?

Thank you ,

Daniel

Thank you, J-F. That is all for now 🙂 We will definitely reach out again when we will need more info - thank you for your support 🙂

Daniel

Hi  J-F

The development of this feature is in progress now , and we have a new question : can you please tell me - are you using / planning to use the OAuth2.0 auth type or are you thinking to use the OAuth2.0 Azure or OAuth2.0 JWT Bearer?

Thanks,

Daniel

Thanks, J-F!

Hi J-F

Can you please let us know what kind of grant type (Client Credentials, Implicit …) are you using between your Apache Kafka and Authorisation server? We would like to cover your setup too in our testing process. 

Thanks,

Daniel

Thank you , J-F

Daniel

Hi all,

seems that I have just found somebody with an similar issue. We also use oauth2 for Kafka topics. But, although the advanced configuration detects the ttl of the token it doesn't automatically generate or refresh it.

We have a similar setup as jfnumainville but had to implement a groovy script in order to have the token generated or refreshed. I had hoped that release 3.41.0 would bring a solution to this, since oauth2 was explicitly mentioned in the release notes, but it apparently didn't.

As this issue is highlighted as solved, I would be interested in the solution.

Regards all and happy testing

Holger

Hi Holger,

Thank you for raising this problem. I will add it our prioritised backlog and we will aim to fix it in one of our next sprints.

Regards and happy testing !

Daniel