1.5.2. Migration to 7.13.0¶
1.5.2.1. Dashboard¶
If you currently have, or have previously had, the OIDC/OAuth2/SSO integration enabled in one of your Dashboards and are upgrading from one of the following versions:
7.8.5-7.8.12
7.9.0-7.9.12
7.10.0-7.10.10
7.11.0-7.11.6
7.12.0-7.12.1
We strongly advise deleting all ApiTokens in your Dashboard configuration database after the update using the following command:
sqlite path/to/dashboard2.db "DELETE FROM axApiToken;"
due to CVE-2026-12593. This deletes both potentially compromised and non-compromised ApiTokens; consequently, you will need to issue new ones.
Display names of OIDC users¶
The Dashboard now stores the display name of each OIDC user in its configuration database and displays it in user management.
The display name is provided by the identity provider upon login; therefore, it is
unknown for users who existed before the automatic configuration database
migration. For those users, a placeholder of the form
<provider name>:<subject identifier> is stored, e.g.,
mycompany-idp:f47ac10b-58cc-4372-a567-0e02b2c3d479.
These placeholder names are expected and require no action: each is replaced by the actual display name the next time the corresponding user logs in. Only users who never log in again will retain the placeholder.
Windows service under a restricted account: error 1053 at start¶
The service wrapper previously re-read its configuration file at each start if the file
was newer than the service registration. This process requires full access to the service
within the
Service Control Manager. Accounts without administrative rights lack this access,
so
the service failed with The service did not respond to the start or control request in a
timely fashion (error 1053). The error Failed to open the service. Access is denied
appears only in the wrapper log axivion_dashboard_service.wrapper.log and in the
Windows event log, rather than in the Dashboard’s own log files.
dashserver install now writes <autoRefresh>false</autoRefresh> into
axivion_dashboard_service.xml. Because a Axivion Suite update does not modify
the configuration of an already registered service, existing installations running the
service under such an account require one of the following actions:
run
dashserver uninstallfollowed bydashserver installagain, oradd the line
<autoRefresh>false</autoRefresh>inside the<service>element of the existingaxivion_dashboard_service.xmlin the Dashboard configuration directory.
Example visualization scripts¶
Several example visualization scripts in
example/reports have been reworked. dashserver copies the example
scripts into <confdir>/modules only if that folder does not exist yet, and
the Axivion Suite update does not modify scripts in the Module Folder. Existing
Dashboard configurations therefore continue to use the old versions, which still
work with 7.13.0.
To use the new versions, copy the files listed below from example/reports of
the 7.13.0 installation into the Module Folder of the
Visualization Creation Interface,
replacing the old files, and reapply any local modifications. The listed
.spec files are no longer used and can be deleted from the Module Folder.
Afterwards, check the options of the affected Custom Visualization gadgets.
visualization_misra_autosar_report.pyThe report is now a grid of gauges, a traffic light for the compliance verdict, bar charts and tables. Every count links into the pre-filtered issue table. Rule links now also work on Dashboards that are served under a base path. The new version requires a Dashboard of version 7.13.0 or later.
Files to copy:
visualization_misra_autosar_report.pyand the foldercompliance_report.No longer used:
misra_autosar_report.spec.Options: unchanged.
visualization_treemap.pyThe area of each file is now proportional to its LOC, also for deeply nested files. Directories that contain nothing but a single subdirectory are merged with it. Clicking a directory label zooms into the directory. Files are colored in five steps from light gray to dark red.
Files to copy:
visualization_treemap.pyandhierarchy.py. The newhierarchy.pyremains compatible withvisualization_hierarchical_edge_bundles.py.No longer used:
treemap.spec.Options: the new option
MCC Aggregationselects how the McCabe complexities of the functions of a file are combined (Sum,MaximumorPer 1000 LOC; defaultSum). WithSum, each function now contributes its McCabe complexity. Previously, it contributed its McCabe complexity plus one. The color value of a file is therefore lower by the number of its functions, so you may need to adjust tuned values ofWhiteandRed.Whitemust now be less thanRed; otherwise the gadget shows an error message instead of the Treemap.
visualization_style_violations_donut.pyThe donut chart now labels its segments with leader lines. If no style violations match, it shows an empty donut instead of a plain text message. This change was already part of 7.12.5 and is relevant only when upgrading from 7.12.4 or earlier.
Files to copy:
visualization_style_violations_donut.py.No longer used:
two_level_donut.spec.Options: unchanged.
1.5.2.2. Architecture Verification¶
Rhapsody Importer¶
The Axivion Suite now provides a new rule Architecture-NativeRhapsodyImporter to import aspects of Rhapsody projects into an RFG. The existing rule Architecture-RhapsodyImporter is now deprecated and will be removed in a future major release. If you are updating from a previous version and wish to switch to the new importer, please contact us. Unlike Architecture-RhapsodyImporter, the rule Architecture-NativeRhapsodyImporter runs on any operating system and does not require a Rhapsody installation. Please note that Architecture-NativeRhapsodyImporter is not a drop-in replacement for Architecture-RhapsodyImporter in terms of configuration. Therefore, replacing the rule will require some refactoring.
Divergent calls to inherited methods now reported¶
A bug has been fixed where divergent calls targeting inherited methods were visible in Gravis but not reported in the Dashboard. After upgrading, these calls are now reported in the Dashboard as well. The reported location for the target points to the base class implementation.
1.5.2.3. Stylechecks¶
MisraC++-5.19.1, MisraC-12.11, MisraC2012-12.4, MisraC++2023-8.20.1¶
A bug has been fixed where overflow/underflow of a compile-time constant caused by
an implicit (uncast) narrowing conversion was not detected; only explicit casts
(static_cast<>/C-style casts) were. After upgrading, these cases are also
reported, which may result in new findings.
To restore the previous behavior of only checking explicit casts, set the new option
check_implicit_conversions to False on the affected rule(s).
Because an implicit conversion has no syntax of its own, if its operand is a cast
that already over/underflows, both are reported at the same source location, which
may appear as duplicate findings. To retain only the message for the cast and
suppress the implicit conversion message, set the new option
deduplicate_implicit_conversions to True (the default is False,
meaning both are reported by default).
CertC-MSC12¶
CertC-MSC12 no longer reports unused/dead-store assignments (the FaultDetection-UnusedAssignments check). This pattern is now exclusively handled by the CERT-C recommendation CertC-MSC13 (“Detect and remove unused values”), which continues to report it. After upgrading, some findings previously reported under CertC-MSC12 will no longer appear; enable CertC-MSC13 to continue detecting them.
FaultDetection-DeadBranches¶
The check now also analyzes switch statements for C/C++; details are
described in the rule documentation.
All new message keys are enabled by default; consequently, new findings may appear
after upgrading. Projects that deliberately keep defensive default
labels can disable the default_never_selected and
default_never_selected_type_limits messages in the rule configuration.
The following rules are also affected, as they use FaultDetection-DeadBranches internally:
AutosarC++17_03-M0.1.2, AutosarC++17_10-M0.1.2, AutosarC++18_03-M0.1.2, AutosarC++18_10-M0.1.2, AutosarC++19_03-M0.1.2,
AutosarC++17_03-M0.1.9, AutosarC++17_10-M0.1.9, AutosarC++18_03-M0.1.9, AutosarC++18_10-M0.1.9, AutosarC++19_03-M0.1.9,
AutosarC++17_03-M0.3.1, AutosarC++17_10-M0.3.1, AutosarC++18_03-M0.3.1, AutosarC++18_10-M0.3.1, AutosarC++19_03-M0.3.1,
MisraC-21.1,
MisraC++-0.1.2,
MisraC++-0.1.9,
MisraC++-0.3.1,
MisraC2012-2.2, MisraC2019-2.2, MisraC2023-2.2, MisraC2025-2.2,
MisraC2012Directive-4.1, MisraC2019Directive-4.1, MisraC2023Directive-4.1, MisraC2025Directive-4.1
The invariant-controlling-expression rules MisraC2012-14.3, MisraC2019-14.3, MisraC2023-14.3, MisraC2025-14.3, and MisraC++2023-0.0.2 report the new constant-switch-condition messages but not the never-selected labels (as these are dead code, which are handled by the dead-code rules above). MisraC-13.7 is unaffected, as a switch condition is always an integer expression and never a boolean operation.
The MISRA rules listed above do not report default_never_selected
messages because their standards also require every switch to have a default
clause (MISRA C:2004 Rule 15.3, MISRA C:2012 Rule 16.4, MISRA C++:2008
Rule 6-4-6); therefore, a defensive default must not be flagged as dead code.
Rules utilizing taint analysis¶
The following changes affect these rules:
CWE-20, CWE-22, CWE-23, CWE-36, CWE-77, CWE-78, CWE-79, CWE-89, CWE-94, CWE-134, CWE-200, CWE-321, CWE-400, CWE-464, CWE-502, CWE-606, CWE-789, CWE-822,
CertC-ENV01, CertC-FIO02, CertC-FIO32, CertC++-FIO32, CertC-INT04, CertC-MEM05,
MisraC2012Directive-4.14, MisraC2019Directive-4.14, MisraC2023Directive-4.14, MisraC2025Directive-4.14
Findings now show the flow from the source to the sink, including the calls it passes through. Flows that were missed when another source had reached the same code first are now reported, which may result in new findings.
Each flow has a class: exact, merged (through merged calling contexts or a possible
alias) or unknown (through abstract memory). Merged and unknown flows are reported with
the new message keys unchecked_external_value_merged and
unchecked_external_value_unknown. Configurations that disable or adjust the
message unchecked_external_value need the same setting for the two new message
keys. The new option highest_reported_flow_class limits the reported classes;
by default, all classes are reported.
When a source reaches more sinks than maximum_reports_per_source_location
allows, the flows of the lowest class are kept first, then flows outside exception
handling, then the flows closest to the source in the call graph; the reported sinks
may therefore differ from earlier versions. The new option
maximum_abstracted_reports_per_source_location (default 1) limits the sinks
per source location that are reached only by merged or unknown flows; set it to 0 for
no separate limit.
The options is_acceptable_use_in_condition, is_relevant_usage and
is_sufficient_preceding_check have been removed; they had no effect in earlier
versions either. JSON configuration files are migrated automatically; Python
configuration files that set these options must be adjusted manually.
1.5.2.4. Azure DevOps Plugin¶
The Axivion Azure DevOps extension is now published on the Visual Studio
Marketplace
as TheQtCompany.axivion0 instead of AxivionGmbH.axivion. The extension
AxivionGmbH.axivion will not receive any further updates.
To migrate, uninstall AxivionGmbH.axivion from your Azure DevOps
organization and install TheQtCompany.axivion0 from the link above.
The task name Axivion-CommentPullRequest is unchanged, so YAML pipelines
do not need to be updated. Pipelines created in the classic editor require the
task to be removed and added again.
1.5.2.5. CLion Plugin¶
In single file analysis run configurations, the variable ${fileDirname} now
expands to the full path of the current file’s directory, as in the VS Code plugin.
Previously, it expanded to the name of that directory only. Run configurations that
rely on the previous value need to be adjusted.
1.5.2.6. Continuous Integration¶
TLS certificates are now verified against the system certificate store¶
When connecting to a Dashboard via HTTPS, CI tools now verify the server
certificate against the operating system’s certificate store (the Windows
certificate store, the system CA bundle on Linux, the macOS Keychain) instead
of the CA bundle shipped with the Axivion Suite. If your Dashboard uses a
certificate issued by a company CA with the root certificate installed in the
system’s certificate store, the connection will now work without further
configuration. If the system’s certificate store does not contain the root
certificate (e.g., in a minimal container image), install it manually or
configure a bundle via REQUESTS_CA_BUNDLE, which will then serve as the
sole trust source for the connection.
MakeIntegration¶
The MakeIntegration now includes a variables option for structured key/value
pairs of Make variables, in addition to the flat options rule
option. The common Make variable configuration CC=irCC CXX=irCXX LD=irCXX AR=irAR
is preconfigured as the default. However, Make variables set in options
take
precedence, ensuring that existing setups continue to work. Additionally,
the
environment variable COMPILE_ONLYIR=1 is set so that the
irCC/irCXX/irAR tools create only Axivion IR files and no
native objects.
For example, if your current setup uses an options setting such as
CC=cafeCC LD=cafeCC, the new effective make call (without any
configuration changes) will be COMPILE_ONLYIR=1 make AR=irAR CXX=irCXX CC=cafeCC
LD=cafeCC. If your project
only uses the CC and LD
variables, it should continue to work as expected. Optionally, you may remove
unnecessary Make variables from the variables option or move your unstructured
options into variables.
However, there may be cases where you need to change your configuration:
your
Makefileuses a value such asAR=ar cruinstead of justAR=ar; in this case, you must also manually configure the flags.you already use
CC=irCC CXX=irCXX LD=irCXXinoptionsto create both native and Axivion IR files simultaneously; in this case, you must remove the environment variableCOMPILE_ONLYIR=1fromenvironmentsto unset it.
Version Control Systems¶
Prior to version 7.13.0, VCS integrations were implemented using two different methods: one that invoked VCS command-line tools via a shell, and another that invoked them without a shell, the latter being more robust against shell injection.
Starting with 7.13.0, all VCS implementations (except for two, see below) use a new, refactored implementation that does not use a shell.
VCS |
Shell usage with <7.13.0 |
Shell usage with >=7.13.0 |
|---|---|---|
ClearCase |
no |
no |
CVS |
yes |
no |
Dimensions |
no |
no |
EASEE |
no |
no |
Fossil |
no |
no |
Git |
no |
no |
Integrity |
yes |
no |
Mercurial |
no |
no |
Perforce |
yes |
no |
Plastic |
no |
no |
PVCS |
no |
no |
RTC |
no |
no |
StarTeam |
no |
no |
Surround |
no |
no |
SVN |
yes |
no |
TFS |
yes |
yes [1] |
VSS |
yes |
yes [1] |
Shadow |
no |
no |
Additionally, the optional settings VCSIntegration/vcs_mapping.vcs_account_callback, VCSIntegration/file_owner.file_owner_callback, and Shadow/file_owner_callback previously used a shell; these have been rewritten to split the arguments before launching the subprocess without a shell. If you have configured commands that use shell functions such as pipes, redirection, or chained commands, you must adjust these configuration settings.
KeilIntegration¶
Due to internal refactoring, the tools build_uvproj, build_uvprojx,
and build_uvmpw no longer support the -k (“continue on error”)
option. If you
rely on this behavior, use --carg=-continue --larg=-continue instead.
RustClippyIntegration¶
The RustClippyIntegration build step has been removed in favor of the new
ImportClippy rule, which can be used independently of the axivion_ci
build phase. Please migrate your configuration to the new rule.
QMLLintIntegration¶
The QMLLintIntegration build step has been removed in favor of the new
ImportQMLLint rule, which can be used independently of the axivion_ci
build phase. Please migrate your configuration to the new rule.
The toolname option has been renamed to executable, and options is now
the additional_args list. The use_json option now defaults to true.
qml_files patterns are now interpreted relative to cwd.