which authentication protocol should I choose for SASL-scram-sha-512 and SSL? #4531
barryzhounb
started this conversation in
General
Replies: 1 comment 3 replies
-
I'm not sure this has an easy answer. Everyone prefers slightly different things, has different security policies etc. I think both are fairly popular. One of the disadvantages of TLS Client Authentication is that it does not use and certificate revocation list. So you cannot easily revoke individual certificates. All you can do is changing the Clients CA. With SCRAM-SHA passwords, this is easier since when you delete a user or its password, it will stop working immediately. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In our project, we have an app outside of OCP that access Strimizi cluster, now we have implemented external routes via port 443 to access kafka topics.
Basically, I understand there are two kinds of authentication and authorization - SASL and SSL.
This is SASL with scram-sha-512, it needs trustore, user name and password for authentication.
This is SSL, it needs truststore and keystore for mutual TLS authentication.
Now, the question is, for authentication SASL-scram-sha-512 and SSL, which one is more practical or more secure ? Which one is used by majority of customers in the real world ? and why?
Beta Was this translation helpful? Give feedback.
All reactions