Validating 3rd Party Certificates before uploading to Swimlane Linux deployments

problem certain 3rd party solutions (active directory, seim, etc ) support and/or require ssl/tsl communications from swimlane, sometimes requiring swimlane to present a certificate for authentication during the creation of the tls connection before uploading a certificate to swimlane, it’s useful to validate that the candidate certificate will facilitate the sought after tls conneciton solution copy the candidate certificate file to the linux host (choose a linux worker node in your swimlane helm or swimlane replicated aka deployment ) the procedure below can be done from the outer linux host, or it can be done from inside the kubernetes pods for swimlane api and tasks modules to validate inside a kubernetes container, follow these instructions to copy the candidate certificate file into the container in question run the following command and inspect its multi line output openssl s client connect hostname 636 cafile candidate certificate crt replace hostname with the fqdn for the host of the 3rd party server in question replace candidate certificate with the name of the certificate file to be validated if the output contains a line that reads “verification error unable to get issuer certificate”, or “verification error unable to get local issuer certificate,” then it will be necessary to find a different candidate certificate file this will likely need to be a full chain certificate file, or the root certificate authority (ca) certificate file for the chain to which the first candidate certificate belongs obtain the next candidate certificate file, copy it to the linux host (and/or the destination container/pod found therein), and attempt to validate it if the output contains a line that reads “verification ok”, then the current candidate certificate is the one that should be uploaded to swimlane