Moving from Legacy RLM Cloud

RLM Cloud has moved to a new web portal at https://cloud.reprisesoftware.com. The legacy interfaces — RLM Cloud Control at rlmcloud.com/manage and the RLM Cloud Control Customer Portal that ran on each license-server machine — have been retired. Bookmarks to the old addresses redirect to the new portal automatically.

For most customers the move changed only the management interface: license servers ran through it without interruption, and applications continued to check out licenses exactly as before.

Warning

One case did break. If you automate provisioning against the RLM Cloud API and your code still calls rlmcloud.com, those requests failed immediately after the cutover, because no redirect to the new address was in place yet. A permanent redirect now exists and they work again. See The RLM Cloud API — new base address.

This page is written for people who already know the legacy system. It maps the old screens onto the new ones, walks through the common tasks in their new form, and states plainly which legacy features do not yet have an equivalent. It is organized in two parts — one for ISV administrators and one for end users (your customers).

Note

If you are new to RLM Cloud and have never used the legacy system, you do not need this page. Start with Overview of RLM Cloud and Getting Started instead.

What Changed

New Addresses

Audience	Legacy address	New address
ISV staff	`https://rlmcloud.com/manage/`	https://cloud.reprisesoftware.com
End users (your customers)	`https://lsNNN.rlmcloud.com/rlmcloud/` — one address per license-server machine	https://cloud.reprisesoftware.com/portal/login — one address for everyone

The single most significant change for end users is the disappearance of the per-machine address. In the legacy system a customer had to know which license-server machine (ls63, ls127, and so on) held their servers, and a customer whose servers were spread across two machines needed two separate accounts. In the new portal there is one address and one account, and a customer sees all of their servers together regardless of which machine each one runs on.

Set Your Password First

Important

Passwords were not carried over from the legacy system. Your account exists, but its old password does not work.

Both sign-in pages display a notice to this effect:

Sign-in notice

Set your password before signing in

Welcome to the new Reprise RLM Cloud portal. Passwords were not carried over from the previous system, so even if you had an account before, use the Forgot password? link below to set your password.

For ISV staff, that is the whole procedure: go to https://cloud.reprisesoftware.com, choose Forgot password?, and set a new password from the emailed link. New passwords must meet the requirements described in Getting Started — at least 12 characters, mixed case, a number, and a symbol.

For end users, there is an extra step, because portal access is off by default on imported accounts. Your ISV must first turn on Allow portal access? for you, which sends you an email titled Set up your RLM Cloud account containing a Set Up Account link. That link expires after 48 hours. Once you have portal access and have set a password, the ordinary Forgot password? flow works for you too.

Three Habits Worth Unlearning

If you used the legacy system daily, three reflexes will no longer serve you.

You no longer write and reread license files by hand. In the legacy system, generating a license did not put it on the server: you pressed GENERATE License, then Write/Update License File on Server, then Reread/Restart Server — three separate steps, and the license text sat in the database in the meantime reading “License not created until you Write/Update License File on Server”. The new portal performs the write, the signing, and the reread as one operation when you add a license, and reports the outcome in a notification. See How License Writes Work.

You no longer press “Update Server Status” and “Refresh Display”. The legacy dashboard did not poll servers on its own; it required one button to contact the servers and a second to redraw the page. The new Cloud Servers page loads current status itself, and refreshes checkout detail every ten seconds while a server row is expanded.

Search boxes are no longer regular expressions. The legacy Select: bar placed a narrow text box under each column and compiled what you typed into a SQL REGEXP predicate, so searching effectively required knowing regex. The new portal has an ordinary search field, usually paired with a column selector, plus sortable columns and server-side pagination.

Part 1 — For ISV Administrators

Signing In

Go to https://cloud.reprisesoftware.com and sign in with your email address and password.

Two differences from the legacy sign-in are worth noting:

You sign in with your email address, not a username. The legacy system used a username of 4–32 characters drawn from letters, digits, ., - and @.
There is no ISV name to supply. The portal determines your ISV from your account. (The ISV Name field exists only on the end-user sign-in page.)

The sign-in page is a page of its own, rather than a form embedded in the header of every screen as it was in the legacy interface.

After five failed attempts an account locks for 15 minutes; an Admin can clear the lock immediately from Admin > Users. See Getting Started.

Where Things Moved

The legacy interface presented a single flat row of tabs. The new portal uses a persistent left sidebar, with tab strips inside individual pages.

Legacy top-level tabs

Legacy tab	New location	Notes
Dashboard	RLM Cloud in the sidebar → the Cloud Servers page	The landing page in both systems. See Cloud Servers.
Customers	Customers → Companies and Contacts tabs	The legacy “Company Info” and “Contact Person Info” sections are now two tabs. See Customers.
Licenses	No single global list. Licenses appear per server on Server Configuration; for a cross-server view use Logs & Reports → Reports.	See Licenses. The legacy inline editing of line item and notes is described under Not Yet Available below.
ID Licensing	ID Licensing → ID Users and ID Groups tabs	No longer a gated beta. See ID Licensing.
Logs	Logs & Reports → Logs tab	See cloud-up-logs.
Products	Products → Products and Bundles tabs	See Products and Bundles.
Profile	Your name in the top-right corner → Profile	No longer a top-level tab.
Reports	Logs & Reports → Reports tab	Available to every ISV. In the legacy system this tab was visible only to Reprise’s own accounts.
Admin	Admin at the bottom of the sidebar → General and Users	Visible to Admin users only, as before. See cloud-up-administration.
About	No equivalent	Current server time appears in the page footer. See Not Yet Available below.

Legacy Admin sub-tabs

Legacy Admin sub-tab	New location	Notes
Audit Trail	Admin → General → Audit Trail tab	Now filterable by action type, user and date range, with a configurable retention period. See Audit Log.
Database	Partly Admin → General → Customization	Only the custom company fields carried over. See Not Yet Available below.
Failover	Admin → General → ISV tab → Configure Failover	See Failover.
Options	Retention settings are under Admin → General	Most legacy options no longer exist because the settings they controlled are now automatic. See Not Yet Available below.
Server Machines	Admin → General → ISV tab	Holds the Generator Settings File and Server Settings File uploads and License Generator State. See ISV.
Users	Admin → Users → System Users tab	Your own staff accounts.
Portal Users	Admin → Users → End Users tab	You no longer choose a license-server machine first. All of your customers’ portal accounts are in one list.
Azure Configuration	Admin → General → Identity & Access	See Identity & Access.
JWT/OIDC Configuration	Admin → General → Identity & Access	See Identity & Access.

Legacy per-server screens

In the legacy dashboard each server row carried a set of small icon links. Those destinations moved as follows.

Legacy screen or icon	New location	Notes
Config → Configure Server	Server Configuration (the gear icon on a server row)	Still the most important screen. See Server Configuration Page.
Usage → RLM License Usage	Expand a server row on Cloud Servers	Per-pool checkout detail is inline and refreshes every ten seconds. See Viewing and Removing Checkouts.
Opts → options-file editor	View Options File on a server row → Server Options	The legacy editing lock and its countdown timer are gone; the page instead asks you to finish within ten minutes. See Editing the Options File.
Stats and Display Server Uptime Stats	No equivalent	See Not Yet Available below.
Reread	Reread Server on a server row; Reread All in the page header	See Server Actions.
Shutdown	Restart Server and Disable Server in the row menu	There is no bare “shut down and leave it down” action; disabling a server is the equivalent intent.
Meter Counter(s)	Edit Meter on a metered pool	See Editing a Meter.
Remove License	The remove action on a checkout row in an expanded pool	Requires Manage.
Provisioning New Server	Add Server on Cloud Servers	See Provisioning a Server.
Named User List	No equivalent	See Not Yet Available below.

Terminology Changes

Most vocabulary carried over unchanged — ISV, product definition, license pool, server machine, license password, failover, debug log, report log. The table below lists only the words that changed.

Legacy term	New term	Notes
RLM Cloud Control	RLM Cloud, in the Reprise Software Unified Portal	The sidebar entry for cloud licensing is RLM Cloud.
Dashboard (tab)	Cloud Servers (page)	Same role: the landing page and the server list.
Fulfillment	License	The legacy interface used both words for one thing; only “license” remains.
Users / Portal Users	System Users / End Users	Two tabs of one Users page rather than two separate admin screens.
Identity-Based Licensing Users and Groups	ID Users and ID Groups, under ID Licensing	Shortened, and no longer a beta feature.
Portal Access: (header label)	Portal role (on an end user’s Profile)	The ISV-staff equivalent is labeled Access level.
Opts	Options File	The abbreviation is gone.
Product Name (in generated license)	Lic. Name in the products table; Product Name on the form	The products table abbreviates several headings: Lic. Type, Token Def., # of Lic.

Access Levels

Staff access levels map one for one, and the hierarchy is unchanged.

Legacy level	New level	Notes
View	View	Read-only.
Manage	Manage	Server operations and edits to existing records.
Edit	Edit	Outranks Manage in both systems — it adds creation and deletion.
Admin	Admin, shown as Administrator on the Profile page	The only level that can reach the Admin section.
Portal ISV Admin	Portal Admin	Reprise-internal in both systems, and not assignable by an ISV. Its legacy purpose — giving one account visibility into every customer’s servers — is no longer needed, because your ordinary ISV staff sign-in already shows all of your customers’ servers.

The legacy numeric levels (View 3, Manage 5, Edit 7, Portal ISV Admin 8, Admin 9) are gone; levels are now named throughout. For the authoritative description of what each level permits, see cloud-up-access-levels.

Note

End users have a separate, shorter set of levels called Portal role. See Access Levels in Part 2.

Workflow Walkthroughs

Onboarding a customer and its server

Legacy: Customers → Add Customer → the Servers icon on the customer’s row → Provision Standard Server, choosing a server machine.

Now:

Go to Customers and press Add Company. Fill in the company details, including any custom fields your ISV has defined.
When the company is created, the portal offers an inline Add Contact action in the confirmation banner. Add the contact who will own the license servers.
Go to Cloud Servers and press Add Server, or open the company from Customers and assign a server from its License Servers card.

The port is still derived from the server instance, and your max_servers limit still applies. See Adding a Company and Provisioning a Server.

Defining a product

Legacy: Products → Add New Product → CREATE Product Definition.

Now: Products → Add Product, which opens Add Product Definition. The fields are substantially the same, including license type, version mode, expiration, metering, token definition, named-user settings, roaming limits, sharing, and the platform toggles for virtual machines, terminal server and remote desktop.

Two changes:

A product definition that contains several licenses is no longer collapsed to a Primary License row with a trailing ellipsis; the table shows the definition and you open it to see its licenses.
You can now group products into Bundles and then issue a whole bundle as one action when adding a license. There was no legacy equivalent. See Product Bundles.

See Creating and Editing a Product Definition.

Issuing a license

This is the workflow that changed most.

Legacy: Configure Server → Add Licenses → fill the form → GENERATE License → Write/Update License File on Server → Reread/Restart Server.

Now: open the server’s Server Configuration page and press Add License. Choose a product — or tick Use Bundle and choose a bundle — set the count, adjust the version and expiration if needed, and submit.

The portal then writes the license file, signs it, and rereads the server as a single operation, and tells you what happened. Three outcomes are possible, and the wording distinguishes them deliberately:

Success — the license was written, signed, and the running server picked it up.
Success, with a note that the reread is running in the background — the license is written and signed on disk, and only the confirmation that the running server reloaded it is outstanding. This is a normal outcome, not a failure, and is especially common when a newly added server is being started.
Failure — the write or signing was refused. The license was not issued.

See Adding a License to a Server and How License Writes Work.

To replace or delete a license, use the Replace and delete actions in the licenses table on the same page. See Replacing and Deleting a License.

Monitoring servers and usage

Legacy: Dashboard → Update Server Status → Refresh Display, then the Usage icon for per-pool detail.

Now: Cloud Servers shows each server with a traffic-light indicator, and you expand a row to see its license pools and, within them, individual checkouts. Nothing needs to be pressed to fetch status.

The indicator has four states — Up, Not serving, Disabled and Down — replacing the legacy configurable colour thresholds. See Status Indicators.

The list has a search field, a Host filter, sortable columns and pagination, and — where a failover is configured — Primary Server and Failover Server tabs. See The Cloud Servers List.

Working with logs

Legacy: the Logs tab, with View / Save / Delete on debug logs and View / Save / Save All / Switch / Reset / List on report logs.

Now: Logs & Reports → Logs. The same actions are present, with two improvements:

The legacy 2–3 MB ceiling on saving a log is gone. The legacy interface told you to use an account on the customer portal to retrieve anything larger; that is no longer necessary. Viewing a debug log in the browser is capped at 4 MB, and the page says so and offers the full file as a download.
Report-log retention is configurable under Admin → General, rather than being a legacy Options setting.

See cloud-up-logs and Report Log Retention.

Running reports

Legacy: the Reports tab — three steps, from a fixed list of report types. In practice most ISVs never saw this tab at all, because it was restricted to Reprise’s own accounts.

Now: Logs & Reports → Reports, available to every ISV. Instead of choosing a predefined report type, you build a report by adding filters from a palette of ten parameters — product, license name, license type, company, server name, host ID, system user, license expiration, line item and notes — with preset date ranges for the expiration filter.

You can export results to CSV, save a report by name, and put a saved report on a Daily, Weekly or Monthly schedule that emails it to chosen recipients. None of that existed in the legacy system.

Changing a failover server

Legacy: Admin → Failover → choose a new failover host → UPDATE → Yes - change failover.

Now: Admin → General → ISV tab → Configure Failover. Choose the new failover for a primary server and save the row.

The operation still takes a while, still shuts down servers on the old failover host and deletes their license files there, and the portal still warns you before it starts. It now reports progress as it goes rather than leaving you on a blank page. See Failover.

Managing users

Legacy: Admin → Users to create staff accounts, typing a password for each one; Admin → Portal Users to create customer accounts, after first selecting which license-server machine to work on.

Now: Admin → Users, with System Users and End Users tabs. You no longer choose a machine, and you no longer choose anyone’s password.

To add a staff member, press New User, supply an email address and an access level. The portal emails an invitation valid for 48 hours; the invitee sets their own password. Accounts show as Pending until then, with a Resend action beside them.

To give a customer portal access, open the end user and turn on Allow portal access?, then choose their Access level. The portal emails them a setup link. The same record carries a separate Allow ID login? switch for identity-based licensing — the two are independent, and enabling ID login does not grant portal access.

Two behaviours have no legacy counterpart: an account can be locked out after repeated failed sign-ins and unlocked by you from this page, and disabling an account immediately ends any session that account currently has open.

New Capabilities

Features with no legacy equivalent, beyond those already described:

API keys — named keys with their own permission level, creation and last-used timestamps, and regeneration, under Admin → General → API Access. See API Users below.
Audit trail filtering and retention — filter by action type, user and date range, and set how long entries are kept.
Product bundles — group products and issue them together.
Bulk product operations — select several products and enable, disable or delete them in one action.
Saved and scheduled reports — described under Running reports above.
Multiple ISVs on one account — if your account belongs to more than one ISV, a switcher appears in the user menu.
Host reachability checking — the Cloud Servers page independently checks that each server machine is reachable, and distinguishes “not yet known” from “unreachable” so a slow check never shows a healthy server as down.
Custom company fields, self-service — you can relabel the ten custom company fields yourself under Admin → General → Customization, and they then become sort options on the Customers list.
Interface conveniences — a collapsible sidebar, real search and sorting, and confirmation dialogs that name what is about to be affected.

Not Yet Available

The following legacy features have no equivalent in the new portal today. Where a workaround exists it is noted; otherwise, contact support@reprisesoftware.com if one of these is important to your workflow.

Legacy feature	Status
Server uptime statistics	The legacy Stats icon and Display Server Uptime Stats screen reported uptime, RLM availability and disk usage over 24 hours, 30 days and a year, broken down by server machine and datacenter. There is no equivalent.
Dashboard summary graphs	The legacy dashboard opened with bar graphs for servers up, failovers up, failovers on standby and total licenses. The Cloud Servers page shows per-server status but no aggregate summary.
Global licenses list with inline editing	The legacy Licenses tab listed every license across all customers and allowed editing the ID, line item and notes directly in the table. The Reports tab can filter and export on line item and notes, but not edit them.
Merging contacts and companies	The legacy Merge Contacts and Merge Companies actions have no equivalent.
Bulk customer import	Legacy Bulk-Load Customer database data accepted a CSV of customers. Companies and contacts must currently be created individually.
Named user list management	Products can still be defined as named-user licenses, with a named-user count. But the legacy Named User List screen for adding and removing the named users themselves — and the customer-portal Personal Licenses screen that did the same for personal licenses — have no equivalent yet. Named user list management is being added back to the portal soon.
Product cloning	The legacy Copy (clone) this product action, which created a `_COPY` duplicate of a product definition, is not available yet. It is being added back to the portal soon.
Database backup, restore and consistency check	Legacy Admin → Database offered a database backup download, a `.sql` upload, and a consistency check. These are now handled by Reprise as part of operating the service.
ISV logo upload	The legacy Upload your LOGO action branded both the admin interface and the customer portal with your logo. The new portal does not currently support ISV branding.
Default server machine	Legacy Set default server machine preselected a machine when provisioning. Choose the machine when adding each server.
Report log auto-save to FTP	The legacy nightly FTP push of report logs is not available. Scheduled report email delivery is a different feature and does not replace it. If you need report logs delivered to a system of your own, the full report log can be fetched through the RLM Cloud API.
Legacy Options settings	Dashboard colour thresholds, server timeout and the options-file edit lock time are gone because the behaviour they tuned is now fixed or automatic.
Broadcast alerts	The legacy dismissible alert banner, used by Reprise to notify ISVs, has no equivalent yet. A new alerts and notification center is coming soon.
About page	There is no page showing portal version, build, database size or a link to the manual. Current server time appears in the page footer.

Advisory: a malformed HTTP header in ISV-built clients

This is unrelated to the portal and to the move. It is recorded here because it concerns software you build and ship, and because you may see it referred to in support correspondence.

What it is. If you build a client for web-services (HTTPS) checkout, the RLM web-services transport that gets linked into it sends one of its HTTP headers with a stray leading space:

Header as sent:  " Accept: application/json"
                  ^ stray leading space

A header line that begins with whitespace is not a new header. Under the HTTP specification it is line folding — a continuation of the header before it. A permissive web server accepts it anyway; a strict one rejects the whole request as malformed.

Which of your builds have it. Any client you built for web-services checkout, because the object file carrying this code is linked in when you build. That includes the HTTP-variant shared library and DLL, not only the example clients we ship. Clients that use RLM’s own protocol rather than web services are unaffected, as are the RLM server daemon and the RLM utilities — those are built against a stub that omits the code path entirely.

Why it has not caused a problem. Web-services checkouts go to the lsNNN license servers, which accept the folded header. Your customers’ checkouts worked before the move and work now.

Note

If your customers’ checkouts are working, they are genuinely working. This advisory is not a warning that something is silently failing.

What you should do: nothing, for now. The fix belongs in the RLM source, which you receive as a prebuilt object rather than as something you maintain. We are correcting it; take the corrected object in a future developer kit and rebuild at whatever point suits you. There is no action to take in the meantime, and nothing to change in your own code.

One thing worth knowing when you plan network changes: this works only because the license servers are tolerant. If web-services traffic from your clients is ever routed through a strict intermediary — a proxy or gateway on your side or your customer’s — those checkouts would begin failing. Worth keeping in mind until the corrected object reaches you.

If you have questions about whether a particular client is affected, contact support@reprisesoftware.com.

Part 2 — For End Users

This part is for people who use RLM Cloud as a customer of a software publisher — you sign in to view your license servers and licenses, not to issue them.

Signing In

Go to https://cloud.reprisesoftware.com/portal/login.

You no longer visit the machine that runs your license servers. The legacy portal lived at an address like https://ls63.rlmcloud.com/rlmcloud/, and which machine you used determined which servers you could see. Now there is a single address, and you can also reach it from the main sign-in page by following Looking for your license portal?

The sign-in page asks for three things:

ISV Name — the name of your software publisher, as RLM knows it. This is new. In the legacy portal your publisher was implied by the address you visited; now you type it. Your publisher will tell you the value.
Email address
Password

Your publisher can also give you a link with the ISV name already filled in, of the form https://cloud.reprisesoftware.com/portal/login/<isvname>. The field remains editable.

Before your first sign-in, see Set Your Password First at the top of this page — your old password does not carry over, and your publisher must enable portal access for your account before you can sign in at all.

After five failed attempts your account locks for 15 minutes. Only your software publisher can unlock it early.

Where Things Moved

Legacy tab	New location	Notes
Dashboard	RLM Cloud in the sidebar → Cloud Servers	The landing page, as before. It now lists your servers across every machine, not only those on the machine you signed in to.
Profile	Your name in the top-right corner → Profile	No longer a tab.
Server Configuration	The gear icon on a server row → Server Configuration	Where you download your license file. Still the page you will use most.
Usage	Expand a server row on Cloud Servers	Checkout detail is inline and refreshes every ten seconds.
Logs	No equivalent	See Not Yet Available below.
Reports	No equivalent	See Not Yet Available below.
Admin → Users	No equivalent	Ask your software publisher to add or remove people. See below.
Admin → Options	No equivalent	The settings it held no longer exist.
Admin → Personal Licenses	No equivalent	See Not Yet Available below.
About	No equivalent	Current server time appears in the page footer.

The sidebar shows a single entry, RLM Cloud. The areas an ISV sees — Products, Customers, ID Licensing, Logs & Reports — are not shown to you.

Workflow Walkthroughs

Downloading your license file

This is the portal’s main purpose, and it works much as before.

Open Cloud Servers, then the gear icon on your server to reach Server Configuration. The card Your Customer Server License holds the CUSTOMER line your users need in their license file. Choose HTTPS or HTTP, then either copy the line with the copy button or press Download License to save it as a .lic file.

If your server has a failover, the card shows the failover license too and the button reads Download Licenses. As before, create two separate license files — one for the primary server and one for the failover.

If you are not using HTTPS, the two TCP ports shown must be open for outgoing connections through your firewall.

The same page shows your Server Information — machine name and IP, server ID, port, license server instance, license password, company and contact — and, in Licenses on this server, the licenses you are entitled to. This last part is new: the legacy portal showed only what was currently checked out, never the entitlement list.

Checking usage

On Cloud Servers, each server has a status indicator — Up, Not serving, Disabled or Down. Expand a row to see its license pools, each showing checkouts in use against the total, and expand a pool to see individual checkouts with user, host, product, version, time and roaming detail.

Checkout detail refreshes every ten seconds on its own. The legacy portal noted that “license usage is updated every time this page is refreshed”; you no longer need to refresh.

You will also find your company and server data is current. The legacy portal read from a local copy that was resynchronised only every six hours, so it could show stale information; the new portal reads live data.

Viewing your options file

Open View Options File on a server row to see the RLM options file in effect for that server.

Your profile and password

Open your name in the top-right corner and choose Profile to see your username, portal role and email address. Reset Password sends a reset email to your address.

If you are locked out or have forgotten your password, use Forgot password? on the sign-in page. You will need your ISV Name and email address. Reset links expire after 30 minutes.

Self-service password reset is new. In the legacy portal there was no working way to reset your own password — you had to ask your software publisher to set a new one and tell you what it was.

Access Levels

Your account has a Portal role, visible on your Profile page. The legacy equivalent was shown in the page header as Portal Access:.

Legacy level	New role	Notes
View	View	Read-only in both systems.
Edit	Edit	The role name carried over, but see the note below — it does not currently grant the write access it did in the legacy portal.
Admin	Admin	As above. Managing your own colleagues’ accounts is not currently possible.

Important

All three portal roles are currently read-only. Edit and Admin are recorded and displayed, but they do not yet grant additional abilities. Concretely, the legacy portal let an Edit user restart servers and delete log files, and an Admin user create and remove accounts for their own colleagues. Neither is possible today. Ask your software publisher to make these changes for you.

New for End Users

One address and one account. Previously, if your license servers were spread across two machines, you needed a separate account on each machine’s portal. Now one account shows all of them.
Set your own password. You receive a setup link by email and choose your own password, rather than being given one.
Reset your own password, as described above.
See what you are entitled to, not just what is checked out — the Licenses on this server table.
Live checkout detail, refreshed every ten seconds.
Choose HTTPS or HTTP when downloading your license file, and download the failover license alongside the primary one.
Current data, with no six-hour synchronisation delay.

Not Yet Available

Legacy feature	Status
Logs	The legacy portal’s Logs tab let you view, download and manage your own servers’ debug and report logs, including a Save All button that packaged every report log for a server into one archive. This was the main reason the legacy portal ran on the license-server machine. There is no end-user equivalent today — ask your software publisher for log files.
Reports	The legacy portal’s Reports tab charted usage over yesterday, the last 7 days or the last 30 days, with totals, peak usage and denial counts. There is no end-user equivalent. Live checkout detail on Cloud Servers shows the present moment only.
Restarting or rereading your servers	Legacy Edit users could reread and restart their own servers, and remove a checked-out license. These actions are not currently available to end users.
Editing the options file	Legacy users could edit their servers’ options file. The options file is currently view-only for end users.
Managing your colleagues’ accounts	Legacy Admin users could create and remove accounts within their own company. Account management is now handled entirely by your software publisher.
Personal Licenses	The legacy portal’s Personal Licenses screen, for maintaining the user, password and options list for a personal license, has no equivalent.
Deleting log files	Not available, following from the absence of the Logs tab.

Part 3 — API Users

Two distinct APIs are often both called “the RLM Cloud API”. They were affected differently by the move, so check which one you use.

The Web Services API — same address

If your application checks out and checks in licenses over HTTP — the API whose endpoints are license.php, logging.php and products.php — nothing changes.

The base address is unchanged: https://lsNNN.rlmcloud.com/rlmapi/current/. These license-server machines did not move.
Authentication is unchanged: the HTTP Basic credentials for your ISV, plus the isv, customer and license_password fields in the request’s header object.
Request and response formats, methods and error codes are unchanged.

No action is required. Your checkout traffic goes to the license servers directly and was not routed through the new service at any point.

The RLM Cloud API — new base address

If you provision customers, products, licenses or servers automatically — typically from a CRM system — you use the API documented in the legacy Appendix G.

What changed: the API now lives at cloud.reprisesoftware.com.

Warning

If your integration still calls rlmcloud.com/api, this is the one thing in the move that broke working code. Immediately after the cutover there was no redirect from the old address to the new one, so requests sent to rlmcloud.com failed outright.

A permanent redirect is now in place at rlmcloud.com/api, so existing integrations work again with no change on your side. You should still update your base address to cloud.reprisesoftware.com rather than relying on the redirect.

What did not change: your existing Secret Key continues to work. Keys issued from the legacy Profile page remain valid, and are still sent in the Secret-Key HTTP header. You do not need to reissue them.

Note

The new portal can also issue API keys of its own, under Admin → General → API Access, with a permission level per key and last-used tracking. These are additional to your existing Secret Key, not a replacement for it.

Frequently Asked Questions

My bookmark still points at the old address. Do I need to change it?

No. Bookmarks to the legacy addresses redirect to the new portal automatically. Updating them is tidier but not required.

My password does not work.

Passwords were not carried over. Use Forgot password? on the sign-in page. If you are an end user and that does not help, your publisher may not have enabled portal access for your account yet.

No. Servers kept running through the move, aside from the possibility of a brief restart, and license checkouts were not affected — they go to the license servers directly, which did not move.

Do my customers need to install anything, or change their license files?

No. The CUSTOMER line in a license file names your license server, not the management portal, so nothing your customers hold needed to change.

I added a license and the notification mentioned a reread running in the background. Did it work?

Yes. The license was written and signed successfully. Only the confirmation that the running server reloaded it was outstanding, which is normal — particularly for a server that was just added. See How License Writes Work.

Where did my customer’s portal account go?

Legacy portal accounts were imported, but with portal access switched off and no password. Open Admin → Users → End Users, turn on Allow portal access? for the account, and the portal will email a setup link.

Why can my customer no longer download their own report logs?

That capability has not yet been rebuilt for end users. It relied on the legacy portal running on the same machine as the logs. Retrieve the logs from Logs & Reports → Logs and pass them on. Note that the legacy 2–3 MB size ceiling no longer applies to you.

My CRM integration started failing after the move. Why?

If it calls rlmcloud.com/api, it failed because there was initially no redirect to the new address. A permanent redirect is now in place, so it works again — but update your base address to cloud.reprisesoftware.com. See The RLM Cloud API — new base address.

Someone mentioned a malformed header in my client. Do I need to act?

No. It is a real bug in the RLM web-services transport that gets linked into clients you build, but your customers’ checkouts go to the license servers, which accept the header. Nothing is silently failing, and the fix will reach you in a future developer kit. See Advisory: a malformed HTTP header in ISV-built clients.

A legacy feature I relied on is listed as not yet available. What now?

Contact support@reprisesoftware.com and describe how you used it. The lists in this page are current status, not final decisions.