Licenses
Overview
Int4 Suite ships as software whose feature set is unlocked by a signed license file that Int4 issues to each customer. The Licenses screen is where the operator installs that file, sees which license is currently in effect, and reviews the history of past uploads.
There is no grace period after expiry and there is no way to deactivate the active license without replacing it; to recover from an expired license the operator must upload a newer file.
Tasks
How to upload a new license
- Open IAM → Licenses.
- Click Upload License in the toolbar. A file picker opens, restricted to files with the
.licenseextension. - Select the license file Int4 issued to you and confirm.
- The list refreshes. The new file appears at the top with Active status, and the previously active license (if any) flips to Inactive with the upload time of the new file as its deactivation moment.
If the file is rejected, an error message appears in the grid area and no change is made to the active license. Common reasons:
- The file is not a valid signed license (corrupt or wrong format).
- The file was signed with a key version that this application build does not recognise — the application is older than the license. Upgrade the application first.
- The license id is on the revocation list shipped with this build.
- The license has already expired.
How to identify the currently active license
The license currently in effect is the row whose Status column shows Active. Only one row can have that status at any time. All other rows are historical uploads that have since been replaced.
Field reference
| Field | Description |
|---|---|
| Customer | The customer name embedded in the signed license file. Identifies who the license was issued to. |
| Template | The license tier template the file references (for example, Int4 Shield Lite). The template determines the baseline feature set and caps; the file may add custom features or override limits on top. |
| App Version | The application version the license was issued against. Used together with the application's own version to filter out template features that require a newer build. |
| Status | Active for the single license currently in effect; Inactive for every previously uploaded license that has since been replaced. |
| Uploaded | When the file was uploaded to this installation. Shown as an em-dash when the value is missing. |
| Expires | The expiry timestamp embedded in the license file. Once this time is in the past, the license stops working immediately — there is no grace period. |
Tips & edge cases
- No grace period on expiry. The moment Expires is in the past, every gated screen and action in the product starts returning a "license expired" error. Plan license renewals ahead of this date.
- Uploading is the only way to switch licenses. There is no separate "activate" or "deactivate" action on a historical row. To replace the active license you upload a new file; to remove the active license you would have to upload a replacement — the system does not support running with no license.
- Historical licenses are never removed. Past uploads remain on this list as an audit trail of what was active and when. They cannot be deleted from the UI.
- A feature can be missing simply because it is outside your edition. Because each edition exposes a different subset of the product, a capability that exists in the software may not belong to the edition you are licensed for — it is scoped out commercially, not broken. The entry-level edition, for example, is purpose-built for a single use case (migrating from SAP PI/PO to SAP Integration Suite) and is intentionally narrow rather than crippled: capabilities aimed at broader, day-to-day testing live in fuller editions. So before assuming a gated screen is a fault, consider whether it simply falls outside your active edition's scope.
Related features
Prerequisites & permissions
To see this page you need the License: Read permission. To upload a new license you also need the License: Write permission. Without License: Write, the Upload License button is disabled. If you reach the page without License: Read, the grid stays empty and the message Insufficient permissions. is shown in place of the rows.
About permissions. Int4 Suite controls what you can see and do through roles and permission groups assigned to your user. Each role grants permissions on a specific resource (for example, Test Case, Automation Object, System Under Test) at one of four levels: Read, Write, Delete, or Execute. Some permissions are further narrowed by project scope, so you may have access to one part of the system but not another.
If a button is disabled or a list comes back empty, missing permissions are the most likely cause. Ask an administrator to review your role assignments, or check IAM → Users if you have the User: Read permission.