-
Notifications
You must be signed in to change notification settings - Fork 789
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS IAM MSK V2 authentication failure when session token expired #976
Labels
Comments
kikyomits
added a commit
to kikyomits/kafka-go
that referenced
this issue
Aug 30, 2022
Use `CredentialsProvider` instead of static `Credentials`. See segmentio#976
kikyomits
added a commit
to kikyomits/kafka-go
that referenced
this issue
Aug 30, 2022
Use `CredentialsProvider` instead of static `Credentials`. See segmentio#976
kikyomits
added a commit
to kikyomits/kafka-go
that referenced
this issue
Aug 30, 2022
Use `CredentialsProvider` instead of static `Credentials`. See segmentio#976
kikyomits
added a commit
to kikyomits/kafka-go
that referenced
this issue
Aug 30, 2022
Use `CredentialsProvider` instead of static `Credentials`. See segmentio#976
kikyomits
added a commit
to kikyomits/kafka-go
that referenced
this issue
Aug 30, 2022
Use `CredentialsProvider` instead of static `Credentials`. See segmentio#976
kikyomits
added a commit
to kikyomits/kafka-go
that referenced
this issue
Sep 3, 2022
Use `CredentialsProvider` instead of static `Credentials`. See segmentio#976
kikyomits
added a commit
to kikyomits/kafka-go
that referenced
this issue
Sep 3, 2022
Use `CredentialsProvider` instead of static `Credentials`. See segmentio#976
kikyomits
added a commit
to kikyomits/kafka-go
that referenced
this issue
Sep 10, 2022
Use `CredentialsProvider` instead of static `Credentials`. See segmentio#976
achille-roussel
pushed a commit
that referenced
this issue
Sep 12, 2022
Use `CredentialsProvider` instead of static `Credentials`. See #976
The resolution for this issue had been merged to main, resolved. #977 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I contributed to
msk_iam_v2
module on the other day but our team recently identified a bug with that.Currently, we give
aws.Credentials
tomsk_iam_v2.Mechanism
but looksaws.Credentials
doesn't automatically refresh the session secret. While looking at AWS GO SDK V2 code, I should have providedaws.CredentialsProvider
to Mechanism.Kafka Version
To Reproduce
msk_iam_v2
module.kafka-go
failed to get authenticated with this errorcould not successfully authenticate to <prefix>.kafka.ap-southeast-2.amazonaws.com:9098 with SASL: [58] SASL Authentication Failed: SASL Authentication failed
The sample configuration of
SASLMechanism
withmsk_iam_v2
is belowExpected Behavior
Automatic rotation of session token as Go SDK V2 does.
Observed Behavior
Failed after session token is expired.
The error message is:
could not successfully authenticate to <prefix>.kafka.ap-southeast-2.amazonaws.com:9098 with SASL: [58] SASL Authentication Failed: SASL Authentication failed
Additional Context
I will make another contribution for this bug fix this week.
The text was updated successfully, but these errors were encountered: