Thanks, checked the ticket which is about a client hostname verification,
but this is not an optimal solution for us; maintaining the allowed hosts
list is not convenient way, once new hosts added you have reissue a new
cert.and deploy it. What we are looking for is for example certificate
validati
You may want to keep an eye on the following ticket:
https://issues.apache.org/jira/browse/CASSANDRA-13404
On 09.07.2018 17:12, Vitali Dyachuk wrote:
> Hi,
> There is a certificate validation based on the mutual CA this is a 1st
> factor, the 2nd factor could be checking the common name of the cl
Hi,
There is a certificate validation based on the mutual CA this is a 1st
factor, the 2nd factor could be checking the common name of the client
certificate, probably this requires writing a patch, but probably some has
already done that ?
Vitali Djatsuk.
