<?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>Why ISVs Use a License Server Instead of Building Licensing In-House</title>
      <dc:creator>Reprise Software</dc:creator>
      <pubDate>Wed, 18 Nov 2026 17:10:55 +0000</pubDate>
      <link>https://dev.to/reprise_software/why-isvs-use-a-license-server-instead-of-building-licensing-in-house-2927</link>
      <guid>https://dev.to/reprise_software/why-isvs-use-a-license-server-instead-of-building-licensing-in-house-2927</guid>
      <description>&lt;p&gt;If you’re building B2B software, licensing gets messy as soon as you start scaling. Developers spend sprints writing custom tracking scripts. PMs can’t offer new pricing models without waiting on engineering. Eventually both teams hit the same wall:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Devs ask:&lt;/strong&gt; Why are we digging through raw logs to figure out how a customer is using their licenses?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;PMs ask:&lt;/strong&gt; Why does offering a floating license or a trial require a code rewrite?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;What a license server like RLM changes&lt;/strong&gt;&lt;br&gt;
A license server sits between your application and your customers’ machines. Your application asks it for a license at startup, and the server decides whether to grant one based on the customer’s license file.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;For PMs:&lt;/strong&gt; License terms such as license type (floating or node-locked), seat count and expiration live in the license file, not in your code. Offering a trial or moving a customer to floating licenses means issuing a new license file, not shipping a new build.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;For devs:&lt;/strong&gt; You integrate one API, once. The server records license usage in human-readable logs, so you aren’t writing and maintaining your own tracking.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;The bottom line:&lt;/strong&gt; Licensing becomes a configuration decision instead of an engineering project. PMs can change packaging without a release, and developers get back the sprints they were spending on license plumbing.&lt;/p&gt;

&lt;p&gt;Learn more about RLM: [&lt;a href="https://reprisesoftware.com/products/reprise-license-manager-rlm?utm_source=dev.to&amp;amp;utm_medium=social&amp;amp;utm_campaign=november&amp;amp;utm_content=dev.to_1"&gt;https://reprisesoftware.com/products/reprise-license-manager-rlm?utm_source=dev.to&amp;amp;utm_medium=social&amp;amp;utm_campaign=november&amp;amp;utm_content=dev.to_1&lt;/a&gt;]&lt;/p&gt;

</description>
      <category>saas</category>
      <category>devops</category>
      <category>security</category>
      <category>architecture</category>
    </item>
    <item>
      <title>Protect Against Virtual Machine Cloning</title>
      <dc:creator>Reprise Software</dc:creator>
      <pubDate>Tue, 20 Oct 2026 14:05:17 +0000</pubDate>
      <link>https://dev.to/reprise_software/protect-against-virtual-machine-cloning-40f1</link>
      <guid>https://dev.to/reprise_software/protect-against-virtual-machine-cloning-40f1</guid>
      <description>&lt;p&gt;As Virtual Machine (VM) software becomes more commonplace, so do cloning licensing systems. By using VMs to replicate whole operating environments on a single host, users are able to clone the system used to limit the number of licenses on that host.&lt;/p&gt;

&lt;p&gt;Since VMs are also usually tied or node-locked to a host, users are able to gain access to extra application licenses, exceeding their licensing agreement. &lt;/p&gt;

&lt;p&gt;Some licensing vendors are helping to combat this issue, like RLM, by adding the capability to disable node-locked licenses or license servers when running on virtual machines. &lt;/p&gt;

&lt;p&gt;This ability allows ISVs to gain more control over how their software is used and ensure they are charging a fair value for licenses. &lt;/p&gt;

&lt;p&gt;Learn more about how to protect against cloning today: &lt;a href="https://reprisesoftware.com/post/licensing-on-virtual-machines?utm_source=linkedin&amp;amp;utm_medium=social&amp;amp;utm_campaign=october&amp;amp;utm_content=dev.to_1"&gt;https://reprisesoftware.com/post/licensing-on-virtual-machines?utm_source=linkedin&amp;amp;utm_medium=social&amp;amp;utm_campaign=october&amp;amp;utm_content=dev.to_1&lt;/a&gt;&lt;/p&gt;

</description>
      <category>devops</category>
      <category>saas</category>
      <category>virtualmachine</category>
      <category>virtualenvironments</category>
    </item>
    <item>
      <title>Maximize License Utility with Token Licenses and Pooling</title>
      <dc:creator>Reprise Software</dc:creator>
      <pubDate>Fri, 18 Sep 2026 15:34:21 +0000</pubDate>
      <link>https://dev.to/reprise_software/maximize-license-utility-with-token-licenses-and-pooling-ec0</link>
      <guid>https://dev.to/reprise_software/maximize-license-utility-with-token-licenses-and-pooling-ec0</guid>
      <description>&lt;p&gt;How do you scale high-concurrency CI/CD builds without paying for static, idle licenses?&lt;/p&gt;

&lt;p&gt;Token pooling lets your automated build pipelines draw license capacity instantly during surges and release it immediately upon completion, giving you peak pipeline scale at a fraction of the cost.&lt;/p&gt;

&lt;p&gt;High-throughput builds. Lean licensing budget.&lt;/p&gt;

&lt;p&gt;Read the guide on token licensing and pooling: &lt;a href="https://reprisesoftware.com/post/maximizing-license-utility-with-token-licenses-and-pooling?utm_source=dev.to&amp;amp;utm_medium=social&amp;amp;utm_campaign=september&amp;amp;utm_content=dev.to_3"&gt;https://reprisesoftware.com/post/maximizing-license-utility-with-token-licenses-and-pooling?utm_source=dev.to&amp;amp;utm_medium=social&amp;amp;utm_campaign=september&amp;amp;utm_content=dev.to_3&lt;/a&gt;&lt;/p&gt;

</description>
      <category>saas</category>
      <category>devops</category>
      <category>productivity</category>
      <category>product</category>
    </item>
    <item>
      <title>Licensing Server-Based Software</title>
      <dc:creator>Reprise Software</dc:creator>
      <pubDate>Wed, 09 Sep 2026 14:19:32 +0000</pubDate>
      <link>https://dev.to/reprise_software/licensing-server-based-software-2pi</link>
      <guid>https://dev.to/reprise_software/licensing-server-based-software-2pi</guid>
      <description>&lt;p&gt;Want to lock your server software to a physical host without complicating client deployments?&lt;/p&gt;

&lt;p&gt;Our latest walkthrough shows you how to configure secure, host-locked licensing that prevents unauthorized multi-host runs while keeping server setup fast and simple.&lt;/p&gt;

&lt;p&gt;Clean host security. Straightforward setup.&lt;/p&gt;

&lt;p&gt;Read the full step-by-step configuration guide: &lt;a href="https://reprisesoftware.com/post/how-to-license-server-based-software?utm_source=dev.to&amp;amp;utm_medium=social&amp;amp;utm_campaign=september&amp;amp;utm_content=dev.to_2"&gt;https://reprisesoftware.com/post/how-to-license-server-based-software?utm_source=dev.to&amp;amp;utm_medium=social&amp;amp;utm_campaign=september&amp;amp;utm_content=dev.to_2&lt;/a&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>saas</category>
      <category>devops</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Reclaim Idle Seats Without Manual Effort</title>
      <dc:creator>Reprise Software</dc:creator>
      <pubDate>Thu, 03 Sep 2026 14:19:15 +0000</pubDate>
      <link>https://dev.to/reprise_software/reclaim-idle-seats-without-manual-effort-936</link>
      <guid>https://dev.to/reprise_software/reclaim-idle-seats-without-manual-effort-936</guid>
      <description>&lt;p&gt;Want to support 100 active users with a lean pool of 30 software licenses?&lt;/p&gt;

&lt;p&gt;RLM's automatic floating license timeout reclaims idle seats instantly, keeping software access seamless and team productivity at peak capacity.&lt;/p&gt;

&lt;p&gt;Maximum seat efficiency. Zero manual effort.&lt;/p&gt;

&lt;p&gt;See how to configure floating license timeouts: &lt;a href="https://reprisesoftware.com/post/floating-license-timeouts?utm_source=dev.to&amp;amp;utm_medium=social&amp;amp;utm_campaign=september&amp;amp;utm_content=dev_1"&gt;https://reprisesoftware.com/post/floating-license-timeouts?utm_source=dev.to&amp;amp;utm_medium=social&amp;amp;utm_campaign=september&amp;amp;utm_content=dev_1&lt;/a&gt;&lt;/p&gt;

</description>
      <category>saas</category>
      <category>devops</category>
      <category>testing</category>
      <category>security</category>
    </item>
    <item>
      <title>How Environment Variables Work Across Shells (And How to Set Them Right)</title>
      <dc:creator>Reprise Software</dc:creator>
      <pubDate>Fri, 21 Aug 2026 20:20:29 +0000</pubDate>
      <link>https://dev.to/reprise_software/how-environment-variables-work-across-shells-and-how-to-set-them-right-1869</link>
      <guid>https://dev.to/reprise_software/how-environment-variables-work-across-shells-and-how-to-set-them-right-1869</guid>
      <description>&lt;p&gt;Environment variables are dynamic flags set outside an application that the application then reacts to. Applications and libraries like RLM read environment variables that they define and rely on them to control runtime options, such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;RLM_ACT_TIMEOUT&lt;/code&gt;&lt;/strong&gt;&amp;nbsp;(adjusts the timeout to the activation server to the value supplied)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;RLM_QUEUE&lt;/code&gt;&lt;/strong&gt;&amp;nbsp;(enables queueing for a license) &lt;/li&gt;
&lt;li&gt;&amp;nbsp;&lt;strong&gt;&lt;code&gt;RLM_ROAM&lt;/code&gt;&lt;/strong&gt;&amp;nbsp;(controls setting up, using, and returning roamed licenses)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;The Environment Process&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A defining characteristic of environment variables is that they are scoped to the specific process where they are set (like a Windows command window or a Unix/Linux shell), and are inherited only by processes that are created by that process. Meaning: if you create 2 command windows and you set an environment variable in window 1, it won't be set in window 2. But if you run an application in window 1, the environment variable will be set in that application.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Easiest Way to Set an Environment Variable&lt;/strong&gt;&lt;br&gt;
Set it in a command window or shell, then invoke the application from that window or shell. &amp;nbsp;For example, if you wanted to set&amp;nbsp;&lt;strong&gt;&lt;code&gt;RLM_DIAGNOSTICS&lt;/code&gt;&lt;/strong&gt;&amp;nbsp;to cause the application to write RLM diagnostic information to the file&amp;nbsp;&lt;strong&gt;&lt;code&gt;diag.txt&lt;/code&gt;&lt;/strong&gt;, you would:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Windows:&amp;nbsp;&lt;strong&gt;&lt;code&gt;set&lt;/code&gt;&lt;/strong&gt;&amp;nbsp;&lt;strong&gt;&lt;code&gt;RLM_DIAGNOSTICS=diag.txt&lt;/code&gt;&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;sh, bash:&amp;nbsp;&lt;strong&gt;&lt;code&gt;export&lt;/code&gt;&lt;/strong&gt;&amp;nbsp;&lt;strong&gt;&lt;code&gt;RLM_DIAGNOSTICS=diag.txt&lt;/code&gt;&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;csh:&amp;nbsp;&lt;strong&gt;&lt;code&gt;setenv&lt;/code&gt;&lt;/strong&gt;&amp;nbsp;&lt;strong&gt;&lt;code&gt;RLM_DIAGNOSTICS diag.txt&lt;/code&gt;&lt;/strong&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Then invoke the application from the window where you set&amp;nbsp;&lt;strong&gt;&lt;code&gt;RLM_ROAM&lt;/code&gt;&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What if your App isn’t Launched from a Terminal?&lt;/strong&gt;&lt;br&gt;
In this case, you can set the environment variable via the Windows control panel:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Bring up the control panel&lt;/li&gt;
&lt;li&gt;Search for “environment” in the search box at the top right&lt;/li&gt;
&lt;li&gt;Click on "Edit environment variables” for your account&lt;/li&gt;
&lt;li&gt;Enter the environment variable name and value&lt;/li&gt;
&lt;li&gt;Click on OK in both windows&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>devops</category>
      <category>beginners</category>
      <category>windows</category>
      <category>saas</category>
    </item>
    <item>
      <title>Creating a Windows Service for RLM Server</title>
      <dc:creator>Reprise Software</dc:creator>
      <pubDate>Wed, 19 Aug 2026 15:48:31 +0000</pubDate>
      <link>https://dev.to/reprise_software/creating-a-windows-service-for-rlm-server-26ee</link>
      <guid>https://dev.to/reprise_software/creating-a-windows-service-for-rlm-server-26ee</guid>
      <description>&lt;p&gt;Here’s a step by step guide on how to configure your process to run as a native Windows Service, which ensures your launching automatically, running persistently in the background, and logging outputs cleanly. &lt;/p&gt;

&lt;p&gt;Steps&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Download an Admin bundle from our&amp;nbsp;website&lt;/li&gt;
&lt;li&gt;Run the installer&lt;/li&gt;
&lt;li&gt;(Optional) Specify the RLM install location&lt;/li&gt;
&lt;li&gt;Open a command prompt (CMD) or PowerShell terminal&lt;/li&gt;
&lt;li&gt;Change Directories to the location where RLM was extracted in step #3. 
For example:cd C:\Users[username]\Documents\Reprise\rlm.v18.0BL1-x64_w4.admin&lt;/li&gt;
&lt;li&gt;Determine which flags you will want to start RLM with. A full list of flags can be&amp;nbsp;found in our documentation.&lt;/li&gt;
&lt;li&gt;Enter your command.

&lt;ol&gt;
&lt;li&gt;Start with&amp;nbsp;rlm&lt;/li&gt;
&lt;li&gt;Include&amp;nbsp;install_service&lt;/li&gt;
&lt;li&gt;-service_name &lt;/li&gt;
&lt;li&gt;-dlog &lt;/li&gt;
&lt;li&gt;Any other flags from step #6
Example:rlm -install_service ‑service_name example-rlm-service ‑dlog my-debug-log.log&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;li&gt;RLM should now be configured to run as a service automatically. You can verify this by checking the services application on Windows:

&lt;ol&gt;
&lt;li&gt;In the start menu, type services, and click the services application from the search results&lt;/li&gt;
&lt;li&gt;Find your service in the list of services. This will be what you named the service in step #7.&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;/ol&gt;

</description>
      <category>windows</category>
      <category>devops</category>
      <category>saas</category>
      <category>architecture</category>
    </item>
    <item>
      <title>Stop License Tampering: Why Digital Signatures Beat “Secret Seeds”</title>
      <dc:creator>Reprise Software</dc:creator>
      <pubDate>Wed, 12 Aug 2026 14:26:24 +0000</pubDate>
      <link>https://dev.to/reprise_software/stop-license-tampering-why-digital-signatures-beat-secret-seeds-4ong</link>
      <guid>https://dev.to/reprise_software/stop-license-tampering-why-digital-signatures-beat-secret-seeds-4ong</guid>
      <description>&lt;p&gt;If you issue plain-text license files, what stops an unscrupulous user from opening the file and changing the license count from 10 to 100 by simply tacking on an extra zero, or from upgrading your v2.0 licenses to v5.0 with a quick edit?&lt;/p&gt;

&lt;p&gt;Without a strong security approach, nothing stops them. This is where digitally signed licenses come in.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How They Work&lt;/strong&gt;&lt;br&gt;
With a digitally signed license, your entitlement data (product, version, expiration date, count, etc.) is passed through a signing algorithm to generate a unique, verifiable signature for that data. &lt;/p&gt;

&lt;p&gt;When your application loads a license file, it checks both the data and the signature.  If the data is ever modified, then the signature for that new data no longer matches the original, rendering the license invalid.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why Public Key Encryption Beats “Secret Seeds”&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Early licensing products used common algorithms that were customized with secret “seeds” to ensure every vendor’s certificate generator could create and validate licenses for its products only.&lt;/p&gt;

&lt;p&gt;However, this approach had a flaw: attackers could reverse-engineer or decompile application binaries, extract the secret seeds, and build counterfeit license generators that worked seamlessly with unmodified applications. &lt;/p&gt;

&lt;p&gt;Modern licensing solves this issue using public/private key technology:   &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Private Key: Resides strictly on your secure build or licensing server to generate and sign licenses. It’s never shipped as part of your software product. &lt;/li&gt;
&lt;li&gt;Public Key: Distributed with your application binary solely to verify the digital signature. &lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>webdev</category>
      <category>architecture</category>
      <category>cryptography</category>
    </item>
    <item>
      <title>System Guide: Setting Up a Centralized Software Licensing Server</title>
      <dc:creator>Reprise Software</dc:creator>
      <pubDate>Fri, 24 Jul 2026 16:07:41 +0000</pubDate>
      <link>https://dev.to/reprise_software/system-guide-setting-up-a-centralized-software-licensing-server-90i</link>
      <guid>https://dev.to/reprise_software/system-guide-setting-up-a-centralized-software-licensing-server-90i</guid>
      <description>&lt;p&gt;Having visibility into user access and seat distribution is crucial for businesses of all sizes, and license servers help you get there.&lt;/p&gt;

&lt;p&gt;Implementing a centralized server allows you to manage, monitor and control your licenses from a single network location. &lt;/p&gt;

&lt;p&gt;Here’s a guide to help you map out the core requirements and configuration to get your server running smoothly:&lt;/p&gt;

&lt;p&gt;System Requirements&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Operating system:  Windows 10 and 11; Apple macOS; or various Linux distributions.&lt;/li&gt;
&lt;li&gt;Processor: An Intel or AMD 64-bit processor &lt;/li&gt;
&lt;li&gt;Additional Software: You might need additional components, such as Microsoft Edge WebView2 Runtime for graphical interfaces.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Configuration Process&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Installation&lt;/li&gt;
&lt;li&gt;Option files: The file contains settings discussing how the license server operates&lt;/li&gt;
&lt;li&gt;Port Setup: Configure the communication ports &lt;/li&gt;
&lt;li&gt;Service Restart: Reload the license server service to apply new settings&lt;/li&gt;
&lt;li&gt;Control Access Panel &amp;amp; Test: Once the server is configured, test the connection from the client machine to ensure it is successful.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Once the process is complete, be sure to regularly monitor and conduct continuous training. &lt;/p&gt;

&lt;p&gt;Check out the full breakdown here:&lt;br&gt;
&lt;a href="https://reprisesoftware.com/post/software-license-server-explained-enhancing-software-asset-management?utm_source=reddit&amp;amp;utm_medium=social&amp;amp;utm_campaign=july&amp;amp;utm_content=dev.to_post_1"&gt;https://reprisesoftware.com/post/software-license-server-explained-enhancing-software-asset-management?utm_source=reddit&amp;amp;utm_medium=social&amp;amp;utm_campaign=july&amp;amp;utm_content=dev.to_post_1&lt;/a&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>devops</category>
      <category>systemadmin</category>
      <category>testing</category>
    </item>
    <item>
      <title>Sandbox Environments for Hosted Activation and RLM Cloud</title>
      <dc:creator>Reprise Software</dc:creator>
      <pubDate>Tue, 21 Jul 2026 17:18:32 +0000</pubDate>
      <link>https://dev.to/reprise_software/sandbox-environments-for-hosted-activation-and-rlm-cloud-28mo</link>
      <guid>https://dev.to/reprise_software/sandbox-environments-for-hosted-activation-and-rlm-cloud-28mo</guid>
      <description>&lt;p&gt;Explore, test, and iterate, with sandbox environments. &lt;/p&gt;

&lt;p&gt;Simulate your real-world licensing setup without the risk, through an isolated environment that gives you total freedom to experiment. &lt;/p&gt;

&lt;p&gt;So what makes a sandbox environment so great? &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Allows you to test without breaking production or affecting end-users&lt;/li&gt;
&lt;li&gt;Try API calls, test error handling, and simulate edge cases without stress&lt;/li&gt;
&lt;li&gt;Experiment with your licensing structure by evaluating delivery workflows and simulating renewals and expirations&lt;/li&gt;
&lt;li&gt;Train your newest developers, product managers, or support engineers on the platform&lt;/li&gt;
&lt;li&gt;Eliminate bottlenecks by testing, learning and being able to deliver with confidence&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If your a Reprise customer using Hosted Activation and RLM Cloud you have access to this environment today. Learn more about how a sandbox could be beneficial to you: &lt;a href="https://reprisesoftware.com/post/welcome-to-your-new-activation-playground-reprise-launches-sandbox-environments-for-hosted-activation-and-rlm-cloud?utm_source=dev.to&amp;amp;utm_medium=social&amp;amp;utm_campaign=july&amp;amp;utm_content=dev.to_post_2"&gt;https://reprisesoftware.com/post/welcome-to-your-new-activation-playground-reprise-launches-sandbox-environments-for-hosted-activation-and-rlm-cloud?utm_source=dev.to&amp;amp;utm_medium=social&amp;amp;utm_campaign=july&amp;amp;utm_content=dev.to_post_2&lt;/a&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>devops</category>
      <category>webdev</category>
      <category>saas</category>
    </item>
    <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>
