X509 certificate (CN=splunkbase.splunk.com,O=Splunk Inc.,L=San Francisco,ST=California,C=US) common name (splunkbase.splunk.com) did not match any allowed names (apps.splunk.com,cdn.apps.splunk.com)
if I use curl ignoring the certificate, it work; if I try to use kafka connect, not work. I imported certificate, create keystore, trying to use it when I create the connector, but not success till now
in kafka connect I keep getting this kind of error -> ERROR [Consumer clientId=consumer-11, groupId=connect-kafka-connect-splunk] Connection to node -2 failed authentication due to: Authentication failed, invalid credentials (org.apache.kafka.clients.NetworkClient:663); I did created and another token, nothing changed
This is one error that I can see on splunk cloud side ->received fatal SSL3 alert. ssl_state='SSLv3 read client key exchange A', alert_description='unknown CA' . The other is about the certificate not match the server name...
Sounds more like an issue with setting up an SSL certificate. Can you please check with the Splunk cloud team?
Generally, this is where the configuration has to be placed: inputs.conf
[http] disabled = 0 index = main enableSSL = 1 serverCert = <full path to your certificate chain pem file> sslPassword = <password for server key used in chain>
yeah, but that is for server that you manage; not sure if any support is offered for free instances. cause I think this is the solution - to create my certificate and support to import it on saas instance. Not understand why HEC is default created with SSL, cause that prevent to use it since certificate is not there...