<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Certificate on The IT Hollow</title>
    <link>https://theithollow.com/tags/certificate/</link>
    <description>Recent content in Certificate on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 31 Aug 2020 14:45:00 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/certificate/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Replace vSphere 7 with Tanzu Certificates</title>
      <link>https://theithollow.com/2020/08/31/replace-vsphere-7-with-tanzu-certificates/</link>
      <pubDate>Mon, 31 Aug 2020 14:45:00 +0000</pubDate>
      <guid>https://theithollow.com/2020/08/31/replace-vsphere-7-with-tanzu-certificates/</guid>
      <description>&lt;p&gt;When setting up your vSphere 7 with Tanzu environment, its a good idea to update the default certificate shipped from VMware with your own certificate. This is a good security practice to ensure that your credentials are protected during logins, and nobody likes to see those pesky certificate warnings in their browsers anyway, am I right?&lt;/p&gt;
&lt;h2 id=&#34;create-and-trust-certificate-authority&#34;&gt;Create and Trust Certificate Authority&lt;/h2&gt;
&lt;p&gt;This section of the blog post is to create a root certificate. In many situations, you won&amp;rsquo;t need to do this since your organization probably already has a certificate authority that can be used to sign certificates as needed. Since I&amp;rsquo;m doing this in a lab, I&amp;rsquo;m going to create a root certificate and make sure my workstation trusts this cert first. After this, we can use the root certificate to sign our vSphere 7 certificates.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
