Mikko Koponen

Should merge now, sorry about the delay.

> My guts feeling is that I want to double check the MSK port where you are connecting with. For IAM authentication, you need to connect via port 9098 for...

> @mtkopone interesting, can you try to connect to your MSK Serverless via CLI? The steps are well-documented in this blog. > https://aws.amazon.com/blogs/big-data/securing-apache-kafka-is-easy-and-familiar-with-iam-access-control-for-amazon-msk > Yeah. The java client library in...

I upgraded to the latest versions, and the same errors still occur against MSK Serverless with the following: ``` github.com/segmentio/kafka-go v0.4.35 github.com/segmentio/kafka-go/sasl/aws_msk_iam_v2 v0.0.0-20221014170723-bef291169c84 ``` Also tried with `InsecureSkipVerify` in `TLSConfig`....

It wasn't the `JoinGroupRequest`. Debugging further.... MSK Serverless reports it would support `MetadataRequest`s in API versions 0 - 11. But looks like any `MetadataRequest` with API version < 6 only...

Sure thing, here you go: Bytes are all in base-10 decimal... ApiVersions request: (clientId = "1") `[0 0 0 11 0 18 0 0 0 0 0 1 0 1...

Yes. The problem remained in main. The metadata call only used v1. The PR above makes it also support v6, which fixes at least that problem.

@ZhangDahe would you be able to test if it works using the fork of #1013 ?

Thank you! We are working on verifying that nothing else is broken with MSK Serverless. Looks good so far. I will update/close this issue once we have more info.

This issue is becoming a blocker for us for using react-native. Also applies to Android. I would love to see it fixed, and can help if necessary.