accepting custom cert -failed

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

accepting custom cert -failed

L0 Member

Have followed this kb however under instance, it is still unable to test successfully when unchecking the trust all certification options under the integrated instance.

 

https://docs.paloaltonetworks.com/cortex/cortex-xsoar/6-1/cortex-xsoar-admin/docker/configure-pytho...

 

upon further checking, have noticed the following empty fields. Not sure if it is supposed to be this way or there are some steps performed wrongly.

Aneo_0-1657771048980.png

 

1 REPLY 1

L2 Linker

Did you add the server configuration key and restart the server? You can verify that the certificate file is being mounted in the container by enabling debug logs, running the /reset_containers command in the playroom (this will restart all of the docker containers on the XSOAR server), and then looking for the `docker run` commands in the server.log. You should see a line similar to this one

 

2022-07-18 13:21:37.0992 debug docker command: /usr/bin/docker run -i --rm --name demistoserver_pyexec-19aae628-2f7f-49b6-8e2b-48fb671e4688-demistopython1.3-alpine--13 --env HTTP_PROXY= --env http_proxy= --env HTTPS_PROXY= --env https_proxy= --log-driver json-file --log-opt max-size=2m -v /var/lib/demisto/python-ssl-certs.pem:/etc/custom-python-ssl/certs.pem:ro,z --env REQUESTS_CA_BUNDLE=/etc/custom-python-ssl/certs.pem --env SSL_CERT_FILE=/etc/custom-python-ssl/certs.pem -v /usr/local/demisto/res/_script_docker_python_loop.py:/tmp/pyrunner/_script_docker_python_loop.py:ro -v /var/lib/demisto/temp/script1815803324:/var/lib/demisto:Z -w /var/lib/demisto demisto/python:1.3-alpine python /tmp/pyrunner/_script_docker_python_loop.py (source: /builds/GOPATH/src/code.pan.run/xsoar/server/services/automation/container.go:326)

 

In this output we can see that the certificate file is being mounted into the container and the environment variables REQUEST_CA_BUNDLE and SSL_CERT_FILE being set with these options

-v /var/lib/demisto/python-ssl-certs.pem:/etc/custom-python-ssl/certs.pem:ro,z --env REQUESTS_CA_BUNDLE=/etc/custom-python-ssl/certs.pem --env SSL_CERT_FILE=/etc/custom-python-ssl/certs.pem

 Also, you should indeed see the environment variables configured when running the !CertificatesTroubleshoot command.

tyler_bailey_0-1658151275671.png

 

 

  • 1239 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!