https://community.splunk.com/t5/Security/SSL-routines-SSL3-GET-CLIENT-CERTIFICATE-no-certificate-returned/m-p/19061#M622 <P>Trying to configure SplunkLightForwarder with SSL for both encryption and mutual authentication, but no connection is made. On the receiver the connection is failing with the error message: ERROR TcpInputProc - Error encountered for connection from host=10.2.3.4, ip=10.2.3.4. error:140890B2:SSL routines:SSL3_GET_CLIENT_CERTIFICATE:no certificate returned</P> <P>On the sender side: sslCertPath=$SPLUNK_HOME/etc/auth/cert/sender.pem sslPassword=password sslRootCAPath=$SPLUNK_HOME/etc/auth/cert/root.crt sslVerifyServerCert=true sslCommonNameToCheck=receiver.example.com</P> <P>On the receiver side: [splunktcp-ssl://12345] disabled = false [SSL] serverCert=$SPLUNK_HOME/etc/auth/cert/reciever.pem password=password RootCA=$SPLUNK_HOME/etc/auth/cert/root.crt dhfile=$SPLUNK_HOME/etc/auth/cert/dhparams.pem requireClientCert=true</P> <P>Thoughts anyone???</P> Thu, 30 Dec 2010 05:15:26 GMT castle1126 2010-12-30T05:15:26Z https://community.splunk.com/t5/Security/SSL-routines-SSL3-GET-CLIENT-CERTIFICATE-no-certificate-returned/m-p/19061#M622 <P>Trying to configure SplunkLightForwarder with SSL for both encryption and mutual authentication, but no connection is made. On the receiver the connection is failing with the error message: ERROR TcpInputProc - Error encountered for connection from host=10.2.3.4, ip=10.2.3.4. error:140890B2:SSL routines:SSL3_GET_CLIENT_CERTIFICATE:no certificate returned</P> <P>On the sender side: sslCertPath=$SPLUNK_HOME/etc/auth/cert/sender.pem sslPassword=password sslRootCAPath=$SPLUNK_HOME/etc/auth/cert/root.crt sslVerifyServerCert=true sslCommonNameToCheck=receiver.example.com</P> <P>On the receiver side: [splunktcp-ssl://12345] disabled = false [SSL] serverCert=$SPLUNK_HOME/etc/auth/cert/reciever.pem password=password RootCA=$SPLUNK_HOME/etc/auth/cert/root.crt dhfile=$SPLUNK_HOME/etc/auth/cert/dhparams.pem requireClientCert=true</P> <P>Thoughts anyone???</P> Thu, 30 Dec 2010 05:15:26 GMT https://community.splunk.com/t5/Security/SSL-routines-SSL3-GET-CLIENT-CERTIFICATE-no-certificate-returned/m-p/19061#M622 castle1126 2010-12-30T05:15:26Z https://community.splunk.com/t5/Security/SSL-routines-SSL3-GET-CLIENT-CERTIFICATE-no-certificate-returned/m-p/19062#M623 <P>Does it work if you specify the default splunk cacert.pem and server.pem? If so, this would indicate a problem with your custom root cert and/or server cert.</P> Thu, 30 Dec 2010 08:39:16 GMT https://community.splunk.com/t5/Security/SSL-routines-SSL3-GET-CLIENT-CERTIFICATE-no-certificate-returned/m-p/19062#M623 araitz 2010-12-30T08:39:16Z https://community.splunk.com/t5/Security/SSL-routines-SSL3-GET-CLIENT-CERTIFICATE-no-certificate-returned/m-p/19063#M624 <P>No I haven't tried with the Splunk PEMs created during install. These are certs built against our PKI infrastructure here, and check out as valid and correct within our environment.</P> Fri, 31 Dec 2010 01:45:25 GMT https://community.splunk.com/t5/Security/SSL-routines-SSL3-GET-CLIENT-CERTIFICATE-no-certificate-returned/m-p/19063#M624 castle1126 2010-12-31T01:45:25Z https://community.splunk.com/t5/Security/SSL-routines-SSL3-GET-CLIENT-CERTIFICATE-no-certificate-returned/m-p/19064#M625 <P>I would suggest a review of the procedure detailed in <A href="http://www.splunk.com/wiki/Community:Splunk2Splunk_SSL_3rdPartyCA">this tutorial </A> to set up splunk-2-splunk communication using SSL certificates signed by a 3rd party certificate authority.</P> <P>The troubleshooting section might help you to pinpoint where the issue with your current configuration is.</P> Thu, 26 Jan 2012 22:12:10 GMT https://community.splunk.com/t5/Security/SSL-routines-SSL3-GET-CLIENT-CERTIFICATE-no-certificate-returned/m-p/19064#M625 hexx 2012-01-26T22:12:10Z