integration splunk with bmc remedy

[ASEP]

Hello all,

im new with splunk, im currently integrating splunk with bmc remedy, with self sign certificate but after config for the cert there is an error like this 




and after i check error from the log  : 

tail -n 100 splunk_ta_remedy_rest_account_validation.log | grep "ERROR"
2025-07-31 12:04:45,394 ERROR pid=3684890 tid=MainThread file=splunk_ta_remedy_rest_account_validation.py:validate:114 | SSLError occurred. If you are using self signed certificate and your certificate is at /etc/ssl/ca-bundle.crt, please refer the troubleshooting section in add-on documentation. Traceback = Traceback (most recent call last):
2025-08-01 13:52:51,828 ERROR pid=758565 tid=MainThread file=splunk_ta_remedy_rest_account_validation.py:validate:114 | SSLError occurred. If you are using self signed certificate and your certificate is at /etc/ssl/ca-bundle.crt, please refer the troubleshooting section in add-on documentation. Traceback = Traceback (most recent call last):

[PrewinThomas]

@ASEP 

If your Remedy server is configured with HTTPS using a self signed certificate, follow the below steps.

-Download the root CA certificate used in your Remedy deployment.
-Copy the contents of the new certificate.
-Navigate to $SPLUNK_HOME/etc/apps/Splunk_TA_remedy.
-Create a new <certs_file>.pem file and add the content of the new certificate. Append the new certificate  content if the file is already present.
-Open the local/splunk_ta_remedy_settings.conf file in a text editor, create a new one if not present.
-Add the ca_certs_path parameter value as below:

[additional_parameters]
ca_certs_path=/opt/splunk/etc/apps/Splunk_TA_remedy/custom_ca_certs.pem # <absolute path to the <certs_file>.pem file>

-Save your changes.
-Restart your Splunk instance.

Refer this doc
#https://docs.splunk.com/Documentation/AddOns/released/Remedy/Configure

Regards,
Prewin
Splunk Enthusiast | Always happy to help! If this answer helped you, please consider marking it as the solution or giving a Karma. Thanks!

[thahir]

Hi @ASEP 
follow the below steps and let me know if you are facing any issues.

1. Export the Remedy SSL certificate from the Remedy server using the command:
echo -n | openssl s_client -connect <remedy_host>:<port> | sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' > remedy_cert.pem
2.Add the certificate to Splunk’s trusted CA bundle:
cat remedy_cert.pem >> /etc/ssl/certs/ca-bundle.crt

Note: take a backup before appending 
3. Restart Splunk 

[thahir]

Hi @ASEP 

The Splunk Add-on is trying to establish an HTTPS connection to the BMC Remedy server, but the SSL certificate presented by Remedy is not trusted by the Splunk environment. This usually happens when the Remedy server uses a self-signed certificate or a certificate from an internal CA that Splunk doesn’t recognize.

[ASEP]

Hi tahir,

thanks for your analysis this problem, do you have a solution ?