Summary

The Reprise License Manager (RLM) Web Administration interface can be configured to use HTTPS for secure communication between administrators and the license server.

This article explains how to enable HTTPS for the RLM Web Server used by the GibbsCAM Network License (NLO) system.

TABLE OF CONTENTS

Overview

By default, the RLM Web Administration interface runs over HTTP:

http://localhost:5054


To secure access to the license server administration interface, RLM can be configured to use HTTPS using an SSL certificate and private key.

Once enabled, the interface becomes:

https://localhost:5054


(or an alternative configured port)
If accessing remotely, replace localhost with the server hostname or IP address.

Prerequisites

Before enabling HTTPS:

  • Administrative access to the RLM server is required

  • You must have:

    • An SSL certificate (.crt or .pem)

    • A private key file (.key)

  • The certificate must match the server hostname (recommended)

  • The GibbsRLMServer service must be installed and functioning

Note: Self-signed certificates can be used for internal networks.

Procedure

See Using SSL Certificates (HTTPS) with RLM | Reprise Knowledge Base 


Step 1: Obtain an SSL Certificate

You can use one of the following:

  • Internal corporate Certificate Authority (recommended)

  • Self-signed certificate (for internal testing)

  • Public CA-issued certificate (rare for internal license servers)

Ensure you have:

  • Certificate file (e.g., server.crt)

  • Private key file (e.g., server.key)


Step 2: Configure RLM to Use HTTPS

  1. Locate the GibbsCAM RLM server installation directory.

  2. Edit the RLM server startup configuration or service parameters.

  3. Add HTTPS-related options to enable SSL.

Typical configuration parameters:

-sslcert server.crt

-sslpriv server.key


The exact file names and paths should match your environment.

  1. Save changes.


Step 3: Restart the RLM Server

After configuration changes:

  1. Stop the GibbsRLMServer service.

  2. Start the service again.

This applies the HTTPS configuration.


Step 4: Access the Secure Web Interface

After restart, open a browser and navigate to:

https://localhost:5054


Or remotely:

https://<server-name>:5054


Step 5: Verify HTTPS Is Active

You should confirm:

  • Browser shows a secure connection (padlock icon)

  • Certificate details match expected server identity

  • RLM Web Administration interface loads normally

Firewall Considerations

When enabling HTTPS:

  • Ensure TCP port 5054 is allowed for HTTPS traffic

  • Update firewall rules if previously restricted to HTTP only

  • Confirm remote access rules allow secure connections

Important Notes

  • HTTPS configuration applies only to the RLM Web Administration interface

  • It does not affect GibbsCAM license checkout communication (port 2764/ISV ports)

  • Misconfigured SSL settings may prevent the web interface from starting

  • Always back up configuration before making changes

Troubleshooting

Problem: Web Interface Does Not Load After Enabling HTTPS

Possible Causes

  • Incorrect certificate path

  • Invalid private key

  • Mismatched certificate and server hostname

  • RLM service failed to start

Resolution

Check the GibbsRLMServer service logs and verify certificate file paths.


Problem: Browser Warning “Connection Not Secure”

Cause

Self-signed certificate or untrusted CA

Resolution

Install the certificate into trusted root store or replace with a CA-signed certificate.


Problem: HTTP Still Works Instead of HTTPS

Cause

HTTPS configuration not applied or service not restarted

Resolution

Restart GibbsRLMServer and confirm startup parameters include SSL options.

Best Practices

  • Use CA-signed certificates in enterprise environments

  • Avoid self-signed certificates for external access

  • Store private keys securely and restrict file permissions

  • Document certificate expiration dates

  • Test HTTPS access before deploying to production users

Expected Result

The GibbsCAM RLM Web Administration interface is securely accessible via HTTPS, improving security for license server administration.

Related Articles

Keywords

RLM, HTTPS, SSL, TLS, Web Administration, 5054, Reprise License Manager, GibbsCAM, Network License, NLO, Security, Certificate