<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Certificates on @PSUStevens Blog</title>
    <link>https://blog.psustevens.com/tags/certificates/</link>
    <description>Recent content in Certificates on @PSUStevens Blog</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>© 2025 David Stevens</copyright>
    <lastBuildDate>Tue, 25 Nov 2025 13:10:38 -0400</lastBuildDate>
    <atom:link href="https://blog.psustevens.com/tags/certificates/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to resolve an untrusted OVA Certificate in vCenter</title>
      <link>https://blog.psustevens.com/2025/11/25/resolve-untrusted-ova-certificate/</link>
      <pubDate>Tue, 25 Nov 2025 13:10:38 -0400</pubDate>
      <guid>https://blog.psustevens.com/2025/11/25/resolve-untrusted-ova-certificate/</guid>
      <description>&lt;p&gt;When deploying an OVA in vSphere 8, it is not uncommon for the workflow to flag the OVA publisher certificate as untrusted.  This can be a significant issue for organizations that prioritize security.  In this blog post, I will cover how to overcome this issue.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-problem&#34;&gt;The Problem&lt;/h2&gt;&#xA;&lt;p&gt;Deploying an OVF Template/OVA is a common operation for a VMware Administrator.  You right-click on the ESX Cluster or an ESX host in the inventory browser and click Deploy OVF Template.  This action initiates the Deploy OVF Template workflow.  Typically, there are ten steps to this workflow.  The first three steps ask for:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
