<?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>Tomcat on TheMacGuy.in</title>
    <link>https://blog.themacguy.in/tags/tomcat/</link>
    <description>Recent content in Tomcat on TheMacGuy.in</description>
    <image>
      <url>https://blog.themacguy.in/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://blog.themacguy.in/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Sun, 20 Jun 2021 22:30:16 +0530</lastBuildDate><atom:link href="https://blog.themacguy.in/tags/tomcat/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Jamf Pro On-premises - Apache Tomcat Certificate update</title>
      <link>https://blog.themacguy.in/posts/2021/2021-06-june/2021-06-20-01-apache-tomcat-cert-update/</link>
      <pubDate>Sun, 20 Jun 2021 22:30:16 +0530</pubDate>
      
      <guid>https://blog.themacguy.in/posts/2021/2021-06-june/2021-06-20-01-apache-tomcat-cert-update/</guid>
      <description>Functionality to issue the Tomcat SSL/TLS certificate from Jamf Pro’s built-in certificate authority — Jamf Pro’s functionality to issue the Tomcat SSL/TLS certificate from the JSS built-in certificate authority (CA) will be discontinued in a future release of Jamf Pro. The release version for this change has not been determined.
Before this change occurs, it is recommended that all on-premise Jamf Pro instances leveraging this functionality switch to a publicly trusted third-party CA to issue the Tomcat SSL/TLS certificate.</description>
    </item>
    
  </channel>
</rss>
