LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

HTTPS Certificate CA Information of the local host is invalid

Solved!
Go to solution

I am working to connect to a website setup by our IT staff, which uses a self signed certificate.  Originally this website was developed using standard http (for internal access), but they want to move to https now.

 

Since I am using LV 2018 and 2020, I need to update the ca-bundle.crt in order to be able to access the site, since the Certification Authority is not in the bundle.

 

I have looked at this knowledge base, and updated my local ca-bundle.crt.

 

I got the .CER and a .p7b (Contains Root and Issuing Certificates) from the server, and copied the within those files from the

 

-----BEGIN CERTIFICATE-----

 

<base 64 encoded values>

-----END CERTIFICATE-----

 

into the C:\Program Files (x86)\National Instruments\Shared\nicurl\ca-bundle.crt.

 

I no longer get the Error 363507: LabVIEW could not verify the authenticity of the server.

 

The new error I get is as shown below (Error 363506):

 

Kenny_K_0-1639586675702.png

 

 

My existing deployed code does not have the ConfigSSL vi in it, where I could point to a new certificate, so I am trying to figure out a way to update the ca-bundle.crt.

 

Kenny_K_1-1639587741214.png

 

Any thoughts on what could be the issue?   My google skills on that error have failed me.

 

Kenny

0 Kudos
Message 1 of 2
(2,431 Views)
Solution
Accepted by topic author Kenny_K

I was able to solve the issue.

 

I downloaded the Cacerts.pem from Mozilla: https://github.com/gisle/mozilla-ca/blob/master/lib/Mozilla/CA/cacert.pem

 

I then extracted the .pfx file from my IT department into a .pem.

 

I copied the contents of the .pem from my IT into the cacerts.pem.

 

I copied the cacerts.pem into the C:\Program Files (x86)\National Instruments\Shared\nicurl and renamed the cacerts.pem to ca-bundle.crt to match what LabVIEW is expecting.

 

This allows me to query the internal HTTPS without issue, and the existing code does not need to be updated.

Kenny

Message 2 of 2
(2,407 Views)