Last modified on November 13, 2023
This feature is currently in closed-access beta. Functionality and documentation may change. Contact StrongDM for more information.
The Version Control page of the Admin UI provides versioning information about all nodes and clients, including node name or user name, node or client version number, any warnings given, when the node or client was registered, IP address, and last heartbeat.
In addition, Version Control is where StrongDM admins may view the current minimum supported version of the client and specify the minimum required version of the client.
StrongDM increments versions as follows:
- n.0-100.0 for each release (such as
- a.b.1 for patch releases (such as
- Releases that are not mentioned in the Release Notes are internal and therefore not described. If looking at a list of releases from a particular software, this might result in the appearance of numbers missing from the sequence, such as
Minimum Supported Version
The minimum supported version of the StrongDM client is version 33.17.0. This version number is given at the top of the Version Control page.
If the user’s client version is below the minimum supported version, the client still functions but uses a deprecated authentication mechanism with a weak security profile. In addition, due to the use of the deprecated authentication mechanism, the client may fail to form linking or peering connections with other gateways at versions above version 33.17.0.
The user sees a warning message in the desktop app and/or CLI if their version is below the minimum supported version.
Minimum Required Version
The minimum required version is the version, if any, that the organization’s administrator(s) specify as the minimum required version for use. Setting a minimum allows admins to prevent users and nodes from accessing StrongDM if they are using a version older than the specified version.
It is optional to set a minimum required version. The default value is “no minimum.”
To change the minimum required version, click edit next to Minimum Required Version and enter the desired version number (for example, XX.YY.Z).
If the user’s client version is below the minimum required version, all non-essential operations are explicitly blocked until the user updates the client, and an error message is displayed in the CLI or desktop app.
Version Control Fields
The following table describes the fields on the Version Control page.
|Name||Name of node or user|
|Actor Type||Gateway, relay, or user|
|Version||Version number of the node or client in format XX.YY.Z, or “unknown-local” if unknown|
|Warnings||Any existing warnings for the node or client|
|Registered At||For nodes, when the node was created; for users, when the user logged in to the client|
|IP||For nodes, the node location of a node; for users, the IP address or “unknown”|
|Last Heartbeat||For nodes, the amount of time since the last heartbeat; for users, the amount of time since the last login|
Search and Filter
You can use search filters to narrow the list of nodes and users.
To use filters, type or copy/paste the following filters into the Search field, with or without other text. Do not use quotes or tick marks.
|Filter||Description||Possible values||Example search|
|Shows the specified node and user authentication type|
|Shows nodes and users that have warnings for the node or client (for example, “Unknown version”)|
|Shows gateways or relays whose last heartbeat was after a specified date or date range; use the calendar selector to choose the date or range; time is optional and may be edited in the Search field (if unchanged, the default time is 7:00 UTC)|
|Shows most recent logins (|
Use the Export CSV button to export all rows or export filtered rows shown on the Version Control page.
See Client Versioning Information for examples of potential warnings or errors that users may experience in the desktop app or CLI if their client does not meet version requirements.