Yes, is there, checked and grey out. I cannot uncheck. So , I cannot remove SSL from the HEC ... View more

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)  ... View more

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... ... View more

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... ... View more

I think is a certificate issue. On Splunk Cloud I see that HEC it have by default SSL enabled. ... View more

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   ... View more

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 ... View more

yes, but I did not found  a way to connect the connector to cloud splunk HEC using https - I get authentication failure all the time 😞 ... View more

it is available for splunk SaaS ? ... View more