Marko Strukelj

If you look at it as Quarkus native build support for Strimzi client, then I agree with @scholzj . But it's actually Quarkus native build support for Kafka client if...

In that case the best strategy indeed seems like working with Quarkus team to make sure their existing example works with Strimzi Kafka OAuth. Let's leave this issue open as...

> You might still want to do something with the exception, though, which is strimzi code. :) True. I will do a PR for that. Thanks for pointing it out.

See https://github.com/quarkusio/quarkus/issues/18398#issuecomment-921712179 for how to fix the issue with native build.

You have to use the unshaded KafkaClients library or package a distribution of Databricks app jar that also shades kafka-oauth-* jars. How exactly to accomplish the second is something you'll...

> The `kafka010` in some of the packages might suggest Kafka 0.10? That would be very old. That's a very good point as well. I think you need at least...

We can probably add some options to allow for this. I'll have to take a closer look.

@torwolf What about the original token you send to introspection endpoint - is it opaque or JWT, and if the latter, does it contain `sub`, and `iat`? It doesn't sound...

It may be latest additions to your branch, but it's a pretty old code from upstream/master. Rebase your changes on top of upstream/master (`git pull --rebase upstream master`) and try...

@Serk72 Maybe the most obvious thing - is reauthentication enabled on your broker? See https://github.com/strimzi/strimzi-kafka-oauth#enabling-the-re-authentication The logs you've pasted show the client refreshing the token, but not the client performing...