> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/system-administration/security/certificate-verification.md). # Certificate Verification ## Description When you use HTTPs, outbound connections are secured using certificates. These connections include ones that are triggered by a call\_webservice part or by the LogicNets runtime for functions like SSO. With HTTPS, other parties cannot view data the system passes; however, there are scenarios where man-in-the-middle attackers can manipulate networks to serve their own keys, thereby compromising any communication. When you enable server certificate verification with the *Use certificate option*, the system checks the validity of the certificate (chain) provided by end-point. A valid certificate must be signed by trusted Certificate Authority (CA). LogicNets requires an up-to-date list of all trusted CAs to perform this check. LogicNets offers 3 options to deliver a list of trusted CAs: ### Use the Operation System Certificate Store This is the recommended option, since the OS certificate store is updated regularly using the OS-specific update routines. Revoked CA certificates are also automatically removed from these stores. LogicNets automatically connects to the Windows Certificate Store. For CentOS, LogicNets expects that all trusted CA certificates are stored in */etc/pki/tls/cert.pem*, which is the default location of CentOS. You can change this location in the e LogicNets configuration *\_session.centos\_certificate\_store\_path*. To use this option the "Security" / "Use OS Certificate Store" option must be enabled in the System Configuration and in case of a call\_webservice the 'Server certificate path' parameter must be left empty. ### Use a Default Local Certificate Store LogicNets provides a default local certificate store in PEM-format. This local certificate store is located in */dat/certificates/CA.pem*. You can change the default location of this store in the configuration file using *\_session.cert\_filename*. To use this option, you must disable the *Security/Use OS Certificate Store* option in the System Configuration module. For call\_webservice, you must leave the *Server certificate path* parameter empty. ### Use a Connection-specific Local Certificate Store This is only available when using the call\_webservice part. You can choose a different certificate store per connection by using the *Server certificate path* parameter. More information about CAs and certificate verification can be found here: More information about the Certificate PEM format can be found here: Install/Update CA certificates on CentOS: --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://community-test.logicnets.com/release-9/platform-documentation/system-administration/security/certificate-verification.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.