Bert Roos

Immediately after logging this issue, I found PR #90, which fixes this issue.

I'm running the latest PowerShell 7 (see below) and the issue still exists ``` Name Value ---- ----- PSVersion 7.3.9 PSEdition Core GitCommitId 7.3.9 OS Microsoft Windows 10.0.22621 Platform Win32NT...

The issue still exists, even in 7.4.0: ``` Name Value ---- ----- PSVersion 7.4.0 PSEdition Core GitCommitId 7.4.0 OS Microsoft Windows 10.0.22621 Platform Win32NT PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…} PSRemotingProtocolVersion...

@deivid-rodriguez Is this still on the radar? We really appreciate the work you did in #6115, but it is quiet for about a month now.

@deivid-rodriguez Thanks a lot! When can we expect to see this in production?

Tested it and it works

No problem! As always, there are multiple ways to approach it. I'd do a slightly bigger refactor as you find in [the attached patch](https://github.com/obsidiandynamics/kafdrop/files/11104590/schema-factory.patch). Note that I have not done...

You need more JARs than just the IAM one. If it still fails after adding all required JARs then please post the log of Kafdrop

Looks like something is wrong in your configuration settings, due to which Kafdrop cannot find Kafka. This is not related to the class loading for SASL.

@andrewchoi5 Have you tested this?