/
opConfig 4 release notes

opConfig 4 release notes

Product Compatibility

Refer to product compatibility to determine supported Operating Systems and Database Versions.

Download opConfig here - https://opmantek.com/network-management-download/opconfig-download/

 

opConfig 4.8.0

Released  May 7, 2026

New Features

  • Introduced a new FIM GUI for generating Command Sets for File Integrity Monitoring, simplifying configuration and deployment. In opConfig → System → Manage Command Sets → Add (+), you can now choose File Integrity Monitoring Command Set. See File Integrity Monitoring (FIM).

  • Added TextFSM structured processing of command outputs using NTC templates, enabling consistent and reliable data extraction. See TextFSM-Based Structured Processing

  • opConfig report-change now consolidates multiple report-changes for a single node into one event, reducing noise and improving signal clarity.

  • Added support for custom scp flags via Administration → Connection → Connect Options input field, including legacy SCP compatibility options. The -O flag (forces legacy SCP protocol) will be automatically ignored on systems that do not support it.

Bug Fixes

Credential Sets

  • Resolved an issue where Credential Sets connection-options returned an empty string instead of a valid JSON array.

  • Credential Sets are now validated for active usage before deletion, preventing accidental removal.

Node Administration

  • Fixed an issue preventing creating a new Group when bulk editing Nodes.

  • CSV export in Administration -> Nodes now correctly serializes array values.

  • connect_options is now validated in the Admin interface, with clearer help text and an array format example.

opConfig GUI — Filters

  • Restored functionality for several filters on the Views → Command Search page that were not applying correctly.

  • Fixed a spurious flash message appearing during node Discovery.

  • Virtual Operator results now surface details on Nodes and Commands excluded by filter_command_candidates, improving visibility into filtered-out candidates.

  • New Virtual Operator jobs no longer fail silently when Credential Sets are missing — a clear error is now raised.

  • Resolved a number of UI inconsistencies in the Scheduled Virtual Operator Job interface.

Event Handling & Connectivity

  • Fixed a regression in opConfig 4.7 where detect-change and report-change operations were not generating NMIS events.

  • opconfig_raise_alert_events now fires for a broader range of connectivity issues, not limited to SSH/Telnet Down states.

opConfig 4.7.0

Released   28 Mar 2025

New Features

Windows Management Instrumentation Support.

Settings

Improvements

  • SAML Authentication added in opConfig, see SAML setup for FirstWave products.

  • Change opConfig to generate a opConfig Node Configuration Change  to be different to the Node Configuration Change event used by NMIS, see opConfig User Manual

  • Update HP Phrasebook

  • Updated OS Rules

  • Improved node editing functionality with timestamps and update tracking when updating node connection values

  • Added capability to force update node configuration and prevent overwriting connection_info from primary.

  • Added friendly revision display to avoid showing "0" when there are no changes, set opconfig_show_friendly_revision = true, (or in the Modules → Administration → Settings → opConfig screen, toggle the Legacy Commands Revision setting)

  • Improved review error search functionality - clicking "review these errors" now shows errors first.

  • Moved command output alerts from sidebar to main body with improved pagination and filtering

  • Compliance Summary gui enhancements

  • Virtual Operator Buttons now allow and carry tag metadata for Virtual Operator jobs. 

Bug Fixes

  • Improved handling of stale database connections

  • Ensured Run Command is called only once

  • Fixed Node Configuration Changes graph to only display data for the current node

  • Fixed breadcrumbs in interface view showing extra HTML

  • Fixed issue with "No commands given to run!" when executing a Virtual Operator job.

  • Fixed dropdown display options behavior with multiple commands.

  • opconfigd.service changed KillMode=control-group 

  • Fixed issue where clicking on a node in the node report would take you to the edit screen

  • Fixed compare command outputs.

opConfig 4.6.1

RELEASED 17 September 2024

  • Compliance Report Enhancements

    • The Compliance Report now includes only opConfig activated nodes when generating the final report.

    • This ensures that only currently activated nodes are considered, providing more accurate and relevant compliance data.

  • Automated Purging of old Compliance Reports

    • A new command-line script has been introduced to automate the deletion of compliance report outputs that are older than a specified number of days.

    • The script can be executed using the following command:

    • ./opconfig-cli.pl act="purge_compliance_output" purge_older_than=23

    • This example command will remove all compliance outputs older than 23 days.

    • This helps in managing storage efficiently and ensures that only recent compliance data is retained.

opConfig 4.6.0

RELEASED 9 July 2024

opConfig 4.5.6

RELEASED 20 May 2024

  • Fixed an issue with Purging Policy being non-deterministic. 
    To address this, a more deterministic approach is applied, where purging rules are explicitly defined and applied based on the command set names or other relevant criteria, ensuring consistent and predictable data retention and deletion.

  • Fixed an issue where the Compare Revision screen displayed an error message even when no node is selected for revision comparison.

opConfig 4.5.5

RELEASED 25 March 2024

  • Fixed issue connecting to certain devices over ssh.

  • Fixed issue when adding connection arguments in Node Admin.

  • New opconfig-cli action, act=create_compliance_report. An action to generate compliance report which show compliant vs non-compliant policies.

  • Report generates the summary of all the compliance policies run against the given node (if no node is given we get data for all active nodes).

  • Report take policy rule name, extract all the rules run against the node and does a value mapping, if it passed or failed.

opConfig 4.5.4

RELEASED 30 January 2024

  • Added support for Debian 11 to the installer

opConfig 4.5.3

RELEASED 21 November 2023

  • New release with Improvements and bug-fixes.

Improvements

Bug Fixes

  • Fixed OS Summary links in opConfig dashboard not showing correct results

  • Fixed OS Summary not filtering out Operating System records

opConfig 4.5.2

RELEASED 30 August 2023

New release with improvements and bug-fixes.

Improvements

  • When the compliance system generates an exception it generates an event.

  • Added option print_command_output=true  for opConfig CLI config command sets.

  • Automatically apply OS detection.  For example, if we know a node is Linux, run some commands to determine if it is Debian, Ubuntu, CentOS, etc.

Bug Fixes

  • Fix deleting an entry in a Command Set would reappear after saving.

  • Fix Command change detection so that opConfig raises an event with title "Node Configuration Change Detected".

  • Fix adding schedule for Config Set from Schedule Configuration Changes screen, it now creates a schedule.

  • Fix pre and post commands disappearing when a Config Set is saved.

  • Fix Command Output screen where the  'Run Command Now' button didn't work when screen width was reduced.

opConfig 4.5.1

Released 02 January 2023

New release with improvements and bug-fixes.

Improvements

  • Bug fix for events raised using command-sets with opConfig.

  • opConfig CLI improvements to add print command output for action push_configset.

  • Bug fixes for test connections.

  • Bug fix for search options.

opConfig 4.5.0

Released  23 November 2022

Big release with an upgraded GUI framework to deliver accessibility enhancements and dark mode.

Improvements

  • This release includes improved Accessibility options, including support for Dark Mode. We have taken the opportunity while we tidied up the screens to change Opmantek to FirstWave. These are new features that are backward compatible with earlier releases.

opConfig 4.4.2

18th August 2022

Support for MongoDB 4.2 please see Upgrading to MongoDB 4.2

opConfig 4.4.1

4th August 2022

This was an internal release

opConfig 4.3.2

8th March 2022

  • Improved mongodb index for command sets.

  • Improved the "Help screen" for Command Sets and Config Sets

  • Added the "Discover OS Info", "Discover Connection Details" and "Test Connection" buttons for nodes in opAdmin

  • New CRUD API for credential sets. 

  • New CLI API for credential sets. 

  • Improved main dashboard load times.

  • Fix to protect a command.

  • New parameter to increase the time out for a plugin per command set: 

    interaction_timeout

opConfig 4.3.1

16 Dec 2021

  • Fix issue where using opConfig in classic auth node would show nodes you shouldn't have access to.

  • Fix issue where virtual operator would break in classic auth mode.

  • Fix issue where scheduling jobs would save the time using the browers timezone not the servers

  • New improvement with a new parameter, compare_to_previous_revision, for config sets to avoid compare revisions. This parameter is specially helpful when the are big files to compare and the config sets are taking a really long time:

 

"commands" : [ { "privileged" : "true", "multipage" : "true", "compare_to_previous_revision" : "false", "use_processing_plugins" : [ "" ], "report_level_min_changes" : null, "active" : "true", "tags" : [ "application", "troubleshooting" ], "use_collection_plugin" : "", "command" : "scp my/file" },

 

opConfig 4.3.0

1 Dec 2021

RELEASED 

  • Updated core dependencies

  • Cookies now support samesite strict, see Security Configurations

  • Fixed issue in checkdaemons.sh with stopping monogdb

opConfig 4.2.7

26 Oct 2021

RELEASED 

This release includes:

  • Spanish translations.

opConfig 4.2.6

21 Sept 2021

RELEASED 

This release includes the following new features:

  • New GUI for editing Config Sets. More information in the following link. 

  • Config set parameters supported: It is possible to add parameters to a config set. More information.

  • Run Virtual operator jobs with groups of nodes:

opConfig 4.2.5

10 Aug 2021

RELEASED

Bug fixes

  • Fixed issue where editing a node in opConfig would overwrite the nodes configuration

  • Test connection error now shows the current error state and if the node name cannot be found it will use the nodes uuid

  • Installer now changes the config option opconfig_default_period from 8d to 2d

opConfig 4.2.4

RELEASED 30 Jul 2021

This release includes:

opConfig 4.2.3-1

RELEASED 29 Jul 2021

Bug Fix

  • Fixes an issue in ./omk/conf/opCommon.json and ./omk/install/opCommon.json by changing the following entry:

    • "omk_show_getting_started_widgets" : true
      becomes
      "omk_show_getting_started_widgets" : "true"

opConfig 4.2.3

Released 13 Jul 2021

Features

  • opConfig installer checks and sets opconfig_raise_alert_events and opconfig_raise_change_events. 

  • Added security content header. This is affecting all the products. The content security policy can be overwritten using the configuration item "security_content_policy".

  • Removed cron line with action import_audit. 

  • Added AIX phrasebook.

Bug Fixes

  • Connection errors are not saved as command revisions.

  • Command collection was not run if no nodes were specified. This may prevent some cron tasks to run. Now, If no nodes are specified, the command will run for all nodes. 

  • Considered just local nodes for license check. 

  • Fixed "Can't call method node on an undefined value" error in some command outputs.

  • Now it is possible to install opConfig on an alternative path using -t.

  • Connect options was not working. 

opConfig 4.2.2

Released 25 May 2021

Bug Fixes

  • Fixed issue in opConfig where a large amount MongoDB connections were created and retained.

opConfig 4.2.1

Released  3 Dec 2020.

Features

  • Command Set Parameters

    • opConfig now supports parameterized command sets. Eg: ping $ipaddress

    • Parameters can be passed in via the command line. Eg parameters.x

    • When creating a new Virtual Operator Job, if you have selected a command set which has parameters, the form will then display "Next" and the second screen will ask you to provide parameters

    • Parameters can also be passed in through derived data

    • Parameters currently have two data types, "string" and "ipaddress"

      • ipaddress is just used for front end validation, the cli does no validation

    • parameters_required => "true" can be set. If the parameters from the cli or gui have not been passed in, opConfig will not run the command

    • Parameters get defined by a top level key and are an array of objects with two keys: parameter and type

      "parameters" : [ { "parameter" : "id", "type" : "String" }, { "type" : "String", "parameter" : "name" } ],

  • Command Set Editor under "System" > "Manage Command Sets"

    • You can delete, update and create new command sets through a visual GUI

    • Only command sets under conf/command_sets.d/ can be modified.

  • Derived Data has new types of table columns to display related jobs or create new virtual operator jobs from. Plugins in opConfig#NewDerivedInformationElementsinopConfig4.2.1

  • Conditions has new types of table columns to display tags, urls and tooltips, More details can be found here Plugins in opConfig#NewReportConditionElementsinopConfig4.2.1

  • New top level key, "active" can be set to "true"/"false" if false the command set wont be loaded

  • New key for commands "active" can be set to "true"/"false" if false the command from that set wont be loaded, other commands set to true will be loaded as part of the set.

 

Bug Fixes

  • Fixed issue where opConfig would report duplicate command sets.

  • Fixed Issue where the trouble shooting button would always display.

  • Fixed issue with logging at debug levels not requested in opconfig-cli

  • Fixed issue where opcharts-cli would not honor different debug levels

opConfig 4.2.0

Released  30 Sep 2020.

Upgrade Notes

The new upcoming release of opConfig 4 will work on Opmantek's latest and fastest platform, however, the currently installed products are incompatible with this upgrade. 
To find out more about this upgrade please read: Upgrading FirstWave Applications

opConfig 4.1.1

released 30th Jul 2020

  • Remote Nodes: Now is possible to work with remote nodes as they were local nodes. They can be also edited, and the changes will be saved in the remote server. Please refer to the opConfig user manual for further information.  

opConfig 4.1.0

released 24th Jun 2020

  • JSON Configuration files: The .nmis configuration files will be replaced by .json files. 

  • New License 2.0 structure used. 

  • Important notice: Due to the JSON configuration files upgrade, when updating to this version, upgrade all OMK Products installed will be required (Not NMIS) to at least X.1. version. It also requires a License update due to the new license structure. 

opConfig 4.0.0

Released   27th May 2020

  • opConfig version compatible with NMIS 9.