<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Clovertech | Michael Sierra | Activity</title>
	<link>https://clovertech.infor.com/members/michaelsierra/activity/</link>
	<atom:link href="https://clovertech.infor.com/members/michaelsierra/activity/feed/" rel="self" type="application/rss+xml" />
	<description>Activity feed for Michael Sierra.</description>
	<lastBuildDate>Thu, 16 Apr 2026 15:21:49 -0400</lastBuildDate>
	<generator>https://buddypress.org/?v=</generator>
	<language>en-US</language>
	<ttl>30</ttl>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>2</sy:updateFrequency>
	
						<item>
				<guid isPermaLink="false">0eb9f48e021c23edb7565afb31483692</guid>
				<title>Michael Sierra replied to the topic Http Certs in the forum Cloverleaf</title>
				<link>https://usspvlclovertch2.infor.com/forums/topic/http-certs/#post-117151</link>
				<pubDate>Tue, 16 Jun 2020 16:56:14 -0400</pubDate>

									<content:encoded><![CDATA[<p>It looks like we are actually using TCLCurl in the script itself. I don&#8217;t know much about cipher sets but we were able to connect to CHIRP without issue until the cert expired in May so I would think if CHIRP had an issue with that then it wouldn&#8217;t have ever worked but I&#8217;m not sure.</p>
<p>&nbsp;</p>
<p>The curl versions are different. I attached screenshots. But&hellip;<span class="activity-read-more" id="activity-read-more-21609"><a href="https://usspvlclovertch2.infor.com/forums/topic/http-certs/#post-117151" rel="nofollow ugc">Read more</a></span></p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">4fc6a3cecc499661a61c0179ec101495</guid>
				<title>Michael Sierra started the topic Http Certs in the forum Cloverleaf</title>
				<link>https://usspvlclovertch2.infor.com/forums/topic/http-certs/</link>
				<pubDate>Mon, 15 Jun 2020 21:25:40 -0400</pubDate>

									<content:encoded><![CDATA[<p>We connect to the CHIRP website with a curl command in a tclscript. We do not use the https-client protocol thread as there were a ton of other issues with it. We recently started getting error when connecting to CHIRP and the vendor confirmed we are using a cert that expired recently. After working with one of our server engineers on this they&hellip;<span class="activity-read-more" id="activity-read-more-21605"><a href="https://usspvlclovertch2.infor.com/forums/topic/http-certs/" rel="nofollow ugc">Read more</a></span></p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">9c80c687d951fb3afdb370b1bfbad2be</guid>
				<title>Michael Sierra became a registered member</title>
				<link>https://clovertech.infor.com/activity/p/21598/</link>
				<pubDate>Mon, 15 Jun 2020 20:14:46 -0400</pubDate>

				
									<slash:comments>0</slash:comments>
				
							</item>
		
	</channel>
</rss>