<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Reprise Software</title>
    <description>The latest articles on DEV Community by Reprise Software (@reprise_software).</description>
    <link>https://dev.to/reprise_software</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3952842%2F0a64e7d6-bf32-4651-a66e-256cf42463ee.png</url>
      <title>DEV Community: Reprise Software</title>
      <link>https://dev.to/reprise_software</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/reprise_software"/>
    <language>en</language>
    <item>
      <title>Using SSL Certificates (HTTPS) with RLM</title>
      <dc:creator>Reprise Software</dc:creator>
      <pubDate>Mon, 13 Jul 2026 18:05:41 +0000</pubDate>
      <link>https://dev.to/reprise_software/using-ssl-certificates-https-with-rlm-439j</link>
      <guid>https://dev.to/reprise_software/using-ssl-certificates-https-with-rlm-439j</guid>
      <description>&lt;p&gt;License administrators are now able to run the RLM web server with SSL certificates, allowing for increased protection though third party identification via web server. &lt;/p&gt;

&lt;p&gt;To implement SSL certificates you can instruct RLM to use HTTPS during startup with the command parameters -sslcert and -sslpriv. But note that certificate files cannot be used if password protected. &lt;/p&gt;

&lt;p&gt;Example code: rlm ‑sslcert /path/to/cert.pem ‑sslpriv /path/to/privkey.pem&amp;nbsp;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How do I create an SSL Certificate?&lt;/strong&gt;&lt;br&gt;
There are many ways that you can procure SSL certificates, here are 3 options:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Purchase it from a certificate provider. These types of certificates are trusted more by OS and browsers.&lt;/li&gt;
&lt;li&gt;Free Services like Let’s Encrypt will provide SSL certificates. &lt;/li&gt;
&lt;li&gt;Create and generate your own. But be warned these self-signed certificates are not trusted by OS or browsers and will display warning messages.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Can’t connect to Web Server after implementing SSL Certificates?&lt;/strong&gt;&lt;br&gt;
Make sure your connecting your RLM server via HTTP. Your URLs should look like:&lt;/p&gt;

&lt;p&gt;-&lt;a href="https://hostname:%5Bport-number%5D" rel="noopener noreferrer"&gt;https://hostname:[port-number]&lt;/a&gt;&lt;br&gt;
-&lt;a href="https://ip-address:%5Bport-number%5D" rel="noopener noreferrer"&gt;https://ip-address:[port-number]&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Got more questions? Check out our article that guides you through the process: &lt;a href="https://reprisesoftware.com/knowledge-base/using-ssl-certificates-https-with-rlm?utm_source=dev.to&amp;amp;utm_medium=social&amp;amp;utm_campaign=july&amp;amp;utm_content=dev.to_post_3"&gt;Using SSL Certificates (HTTPS) with RLM&lt;/a&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>devops</category>
      <category>saas</category>
      <category>architecture</category>
    </item>
  </channel>
</rss>
