Skip to content
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

fix: use correct mechanism name for broker compatibility #411

Merged
merged 1 commit into from
Jun 27, 2019

Conversation

kjdelisle
Copy link
Contributor

The broker module expects AWS as the mechanism name.

Fixes #410

The broker module expects `AWS` as the mechanism name.
@Nevon
Copy link
Collaborator

Nevon commented Jun 26, 2019

Sorry about that! I wanted to avoid the AWS name because it seemed probable that AWS would eventually release some other identity product, so it seemed prudent to specify IAM.

@kjdelisle
Copy link
Contributor Author

@Nevon Believe me, I know the frustration. I initially created the plugin with AWS-IAM as the mechanism, and when that ran aground, I tried AWS_IAM and had the same problems!

@tulios tulios merged commit fcfeef6 into tulios:master Jun 27, 2019
@kjdelisle kjdelisle deleted the protocol/aws-mechanism-fix branch June 27, 2019 14:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

AWS SASL Mechanism Name is incorrect
3 participants