Are you sure this is caused by the vCenter certificate and not the certificate included In the OVF?
Can you import the same via the Web CLient without issue?Blog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz1 person found this helpful
just tried it with the Web Client and it looks like you're right - the problem is with the self-signed certificate bundled with the OVA. This is an official NSX-T OVA that I downloaded from VMware. If I click "Proceed Anyway" then it's imported successfully.
It looks like there is no functionality to ignore OVA certificate with "New-ContentLibraryItem"? Perhaps this can be added in the future?
I would suggest to open an SR for this.
I agree that an official OVA should not contain self-signed certificates.
And yes, the option to bypass the certificate check is missing on the cmdlet.
I would suggest to launch an idea for this at VMware PowerCLI
In parallel inform your TSABlog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz
Just in case someone else hits this - until the cmdlet option is added, a solution is to unzip the ova, remove the .cert file, and import it as ovf.