<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Nicholas Cole on Medium]]></title>
        <description><![CDATA[Stories by Nicholas Cole on Medium]]></description>
        <link>https://medium.com/@nicholas.cole_8623?source=rss-531d61836051------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*YfK86Q1ZcxFAmP_0SiXUJw.png</url>
            <title>Stories by Nicholas Cole on Medium</title>
            <link>https://medium.com/@nicholas.cole_8623?source=rss-531d61836051------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:20:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nicholas.cole_8623/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Automated Website SSL Cert Validation Using Conductor]]></title>
            <link>https://medium.com/@nicholas.cole_8623/automated-website-ssl-cert-validation-using-conductor-baee2b584319?source=rss-531d61836051------2</link>
            <guid isPermaLink="false">https://medium.com/p/baee2b584319</guid>
            <category><![CDATA[netflix-conductor]]></category>
            <category><![CDATA[orkes]]></category>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[orchestration]]></category>
            <dc:creator><![CDATA[Nicholas Cole]]></dc:creator>
            <pubDate>Fri, 03 Apr 2026 22:19:00 GMT</pubDate>
            <atom:updated>2026-04-03T23:06:15.584Z</atom:updated>
            <content:encoded><![CDATA[<p>Many of us have faced the issue of needing to check certificate expiry dates manually and going through the process of renewing these certificates.</p><p><strong>What are SSL Certificates?</strong></p><p>SSL certificates are cryptographic keys that verify a website’s identity and encrypt traffic between browser and server. These certificates expire in order to ensure keys rotate regularly, preventing compromise. SSL Certificates are required for HTTPS.</p><p><strong>What are some of the challenges?</strong></p><ol><li>When an SSL certificate expires, your website goes down for all HTTPS traffic — causing immediate operational impact.</li><li>Some cloud providers offer managed certificates, but this isn’t always available, free, or compatible with existing enterprise configurations.</li><li>Building custom code to scan all your URLs is possible, but introduces complexity around resiliency, performance, and maintenance.</li></ol><p><strong>This is where Orkes Conductor comes in!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FLuTO3uJzcdlEIdXEBe9Ng.png" /></figure><p>Conductor is an open-source workflow orchestration engine <strong>originally built at Netflix</strong>. It lets you define business logic as a JSON workflow — no application framework needed.</p><p>Workflows run on a central server, execute tasks via workers you write in any language, and are fully visible through a built-in UI.</p><p><strong>For this use case</strong>, we define a workflow that fans out SSL certificate checks across multiple clients in parallel, collects the results, and routes alerts based on severity — all without writing glue code or building a custom scheduler.</p><p><strong>Example Implementation</strong></p><p>I have built an implementation that you can try for yourself by following a few simple steps.</p><p><strong>First</strong>, take a look at this diagram representing the workflow sequence:</p><p>The workflow prepares inputs for each client, fans out SSL checks in parallel, joins the results, computes severity, creates Jira tickets for any client failures, and routes alerts to Slack, Email, and PagerDuty depending on severity.</p><p><strong>Note: </strong>The integrations are mock integrations; however, you may find integration guides by clicking these links: <a href="https://orkes.io/blog/automating-slack-greetings-to-community-with-orkes-conductor/">Slack</a> , <a href="https://orkes.io/content/tutorials/using-idempotency-keys-in-webhook-triggered-workflows">Jira </a>, and <a href="https://orkes.io/content/templates/alerting/scanning-an-endpoint-and-triggering-pagerduty-alert">PagerDuty</a> . Here, we are focusing on showcasing the workflow logic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AlMSYqMPbEfEM-muSovIig.png" /><figcaption>Flow Diagram</figcaption></figure><p><strong>Let’s get this running on your local!</strong></p><p>Pre-Reqs:</p><ul><li><a href="https://git-scm.com/">Git</a></li><li><a href="https://www.python.org/downloads/">Python 3.10</a></li><li><a href="https://nodejs.org/en/download">npm</a>(will come with NodeJS)</li></ul><ol><li><strong>Navigate to working directory</strong> you would like to clone the repo to such as ~/Users/testUser/projects</li><li><strong>Run</strong> git clone <a href="https://github.com/NicholasDCole/conductor-certhound.git">https://github.com/NicholasDCole/conductor-certhound.git</a></li><li><strong>Navigate inside of the folder and run the following commands:</strong></li></ol><pre>npm install -g @conductor-oss/conductor-cli<br><br>conductor server start</pre><p>4. <strong>Validate below logs show and server is up and running</strong></p><pre>Checking Java version...<br>Java 21 detected<br>Using cached server JAR: /Users/test/.conductor-cli/server/oss/latest/conductor-server.jar<br>Starting OSS Conductor server (version: latest) on port 8080...<br>Server starting (PID: 65801)...<br>Logs: /Users/test/.conductor-cli/server/conductor.log<br>Waiting for server to be ready...<br><br>Conductor server is ready!<br>  API: http://localhost:8080/api<br>  UI:  http://localhost:8080<br><br>Open http://localhost:8080 in your browser to access the Conductor UI<br><br>Use &#39;conductor server stop&#39; to stop the server<br>Use &#39;conductor server logs&#39; to view logs</pre><p>5. <strong>Install Python Dependencies and start our Python Worker.</strong></p><p>The worker is a long-running process that polls Conductor for tasks and executes them:</p><p>Open up your terminal and copy-paste <strong>all below commands</strong> into it</p><p><strong>Important:</strong> Keep this running in a separate terminal.</p><pre>python3 -m venv .venv    <br><br>## Mac/Linux                                                                                                                           <br>source .venv/bin/activate    <br><br>## Windows <br>## .venv\Scripts\activate  <br>                                                                                                                    <br>pip install -r workers/requirements.txt<br><br>python workers/check_ssl_certs_worker.py</pre><p>6. <strong>Visualize the workflows in Conductor</strong></p><p>The JSON files for our 2 workflows are defined in <a href="https://github.com/NicholasDCole/conductor-certhound/tree/main/workflows">https://github.com/NicholasDCole/conductor-certhound/tree/main/workflows</a></p><p>The 2 Workflow Definitions will be visible at <a href="http://localhost:8080/">http://localhost:8080</a> in the definitions tab after running the python worker above (it will automatically create these definitions for you)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-QYzAK3EXmVgVua26M1zRQ.png" /><figcaption><strong>cert_hound_workflow</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*se2WAL3FXlO0z9oD-TZDsw.png" /><figcaption><strong>cert_hound_monitor_workflow</strong></figcaption></figure><p>7. <strong>Execute the workflow</strong></p><p>The — sync flag blocks until completion and prints the output:</p><pre>conductor workflow start -w cert_hound_monitor -f test_monitor_input.json --sync</pre><p>You will be able to view following execution result by clicking on the executions tab and clicking into the cert_hound_monitor (top-level workflow) execution. <a href="http://localhost:8080/executions">http://localhost:8080/executions</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V9SAzUPkPDO1kJeICxRgsg.png" /><figcaption>Executions Window</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P619BwdJtlP4rsIaOBInVQ.png" /><figcaption>Execution Result</figcaption></figure><p>8. <strong>Validate output against sample output on </strong><a href="https://github.com/NicholasDCole/conductor-certhound/blob/main/README.md#sample-output"><strong>GitHub</strong></a></p><h3><strong>Congratulations!</strong></h3><p>You’ve spun up a Conductor Server and executed a full workflow on your local machine!</p><h3><strong>Important Takeaways</strong></h3><p>I intentionally built this as a complex example — URLs are grouped by client so that a failure for one client doesn’t block the others.</p><p>In this case, I set up an invalid input for the Initech client; however, we marked the Dynamic Fork Join as optional: true , meaning that our workflow is able to mark our JOIN step as COMPLETED_WITH_ERRORSinstead of FAILED and continue the workflow.</p><p>This workflow can be further extended to integrate fully with Slack/Email/Jira/etc. depending on business use-case. Feel free to copy/fork the source code and extend as you wish.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=baee2b584319" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>