Skip to main content

Hi Team,

As per the below KB article, for SSL/TLS connection error, we need to import Splunk certificate chain to U-Series Appliance and disable the client authentication check on BI Configuration.

How to fix SSL/TLS connection for Password Safe Cloud, because we don't have access to backend U-Series Application and BI Configuration? 

BeyondInsight / Password Safe - Splunk Test Connector error: "Failed to open connection" - Splunk test script

Hello ​@Prudhvi Keertipati, I would open a case with support to assist you in making your adjustments. In the meantime, take a look at this BeyondInsight / Password Safe - Password Safe Cloud troubleshooting, see if you are able to achieve what you are looking to do, this article will also assist in future troubleshooting so it is good to have regardless.


Do the Password Safe Cloud use Resource Brokers Connector Services to connect with the Splunk and other connectors?


Below are the steps and configuration we perform for the successful Password Safe Cloud and Splunk Cloud integration.

On Password Safe Splunk Connector: 

  • Splunk Cloud URL must be in the format:  https://http-inputs-<instancename>.splunkcloud.com (URL format will be different for Splunk Enterprise and Splunk Gov Tenants)
  • As per Splunk, HEC Port for Splunk Cloud Prod instance is 443 and Splunk Cloud Trail instance is 8088. Select the appropriate port.
  • Enter the HEC Key provided by Splunk Admin.

On Splunk Cloud :

HEC option, “Enable indexer acknowledgement” must be unchecked.


Reply