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

Security based on SCRAM for kafka backend should also consider plain listener #32

Closed
rgordill opened this issue Jun 10, 2020 · 3 comments
Labels
1.1.x Issues for 1.1.x release Quality It's not a bug, but negatively affects user experience or may cause problems in the future

Comments

@rgordill
Copy link

Currently, the operator needs trustStoreSecretName to connect using tls.

However, kafka can be configured also with plain connection, but using SCRAM for authentication/authorization. The operator should consider ssl in scram security as optional.

@jsenko jsenko added the Quality It's not a bug, but negatively affects user experience or may cause problems in the future label Jun 17, 2020
@didentifier
Copy link

Can I mount the secrets from strimzi user secret? Also is there only support for trustore, do I not need a keystore?

@jsenko jsenko added the 1.1.x Issues for 1.1.x release label Apr 29, 2021
@rgordill
Copy link
Author

As latest version is jumped to 2.x, it makes no sense this issue anymore.

@amruthpremjith
Copy link

Would it be possible to use scram with plain listeners now, could you please provide some kind of documentation for it? I am currently running a strimzi kafka with scram-sha-512 authentication on plain listeners and was thinking of using it for apicurio also.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.1.x Issues for 1.1.x release Quality It's not a bug, but negatively affects user experience or may cause problems in the future
Projects
None yet
Development

No branches or pull requests

4 participants