-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
MSK - failed to create ACL and Topic using SASL/SCRAM #331
Comments
|
It's possible that your sasl user doesn't have the privileges yet. Try running
Once it works, remember to scope down the permissions. You probably only need the |
This comment was marked as resolved.
This comment was marked as resolved.
@rssaini01 I can create & destroy ACL via SASL_SSL, as shown below: kafka_acl.brokertopic will be destroyed(because kafka_acl.brokertopic is not in configuration)
Plan: 0 to add, 0 to change, 1 to destroy. Do you want to perform these actions? Enter a value: yes kafka_acl.brokertopic: Destroying... [id=User:broker|*|All|Allow|Topic|TEST_|Prefixed] Apply complete! Resources: 0 added, 0 changed, 1 destroyed. |
@rssaini01 pls set up as below: provider "msk" { |
Getting an error when trying to create ACL or Topic to MSK cluster using SASL/SCRAM auth and also public access is on.. so I'm using public endpoint of brokers
getting the below error for ACL
this one for topic
The text was updated successfully, but these errors were encountered: