This article includes a list the new features and bug fixes that are included in Lucent Sky AVM version 1804, as well as known issues of this release.
For more information about this release, visit the blog post Lucent Sky AVM version 1804 released.
Updates in Lucent Sky AVM version 1804
-
Search (second phase) - Through the search interface, users are able to filter applications by ownership, framework, runtime, and the status of their last scan. Additionally, users can search for specific applications with keywords in their name or tags.
-
Maven support (beta) - Java applications using Maven are now supported natively, without the need of making a WAR file first. Lucent Sky AVM will automatically download required libraries and build the application according to its pom.xml. To scan an application using Maven, set 'JavaBuild' to 'Maven' and 'JavaSourcePath' to its source path.
-
Suppression improvements - Result suppression is now available for all results, including file-based ones. Additionally, multiple results can now be suppressed in batch.
-
Updated scan result codes - Scan result codes were redesigned to give user more information when a scan failed or completed with warnings. To learn more about the new scan result codes, including how to migrate integrations using the legacy result codes, visit the article Lucent Sky AVM scan result code.
-
Bug fixes - Several issues were addressed in version 1804.
-
New version naming scheme - A minor but most visible change, Lucent Sky AVM has adopted a new version naming scheme.
List of fixes included in Lucent Sky AVM version 1804
Unable to filter applications that have scans in progress using the API
When using the API to retrieve applications with its last scan in a certain status, it is not possible to retrieve applications with its last scan in progress. This issue is due to an incorrect filter being used by the API.
This issue has been resolved in Lucent Sky AVM version 1804.
The specified project file of a .NET application is ignored
The specified project file of a .NET application is ignored and not being considered when the compiler is choosing the entry project. This issue is due to a bug in the API and first appeared in v5.0.
This issue has been resolved in Lucent Sky AVM version 1804.
When binary scan failed, an incorrect scan result code is shown
When binary scan failed, an incorrect scan result code is shown (such as -99).
This issue is due to a bug in the analysis management interface and first appeared in v5.0.1.
This issue has been resolved in Lucent Sky AVM version 1804.
Known issues of Lucent Sky AVM version 1804
The knowledge base article included in error and warning messages of a failed or incomplete scan is incorrect
The knowledge base article included in error and warning messages of a failed or incomplete scan is incorrect. The linked article is for a previous version of Lucent Sky AVM.
The linked article includes a link to the correct article. This issue has also been addressed in Lucent Sky AVM version 1805.
The application filters on the application list page do not work in Internet Explorer,
When using Internet Explorer to access the web UI, selecting an option in the framework filter or the scan status filter does not cause the application list to display a filtered list. Instead, all applications are still shown.
This issue has been addressed in Lucent Sky AVM version 1805.
When scanning a Java application, an unlocalized error message appears if the scan failed during pre-analysis
When scanning a Java application, an unlocalized error message appears if the scan failed during pre-analysis. This issue is due to localization mismatch in the resource files.
This issue has been addressed in Lucent Sky AVM version 1805.