OctoSAM 1.10.9 Release

OctoSAM 1.10.9 Release can be downloaded from the Filebase.

Technical documentation

Supported environments - minimum requirements

New Features

• Dark theme for the Web UI, respects browser appearance settings for newest Chrome and Edge browsers.
• New themes 'Dark' and 'Light' for the Octopus2 GUI (beta)
• Improved high DPI support in Octopus 2 GUI (beta)
• Can now define a default set of selected organizations in OctoWeb
• RBAC per organization Read and Update privileges
• Upload server OctoCollect now supports both Windows IIS and Linux nginx environments
• Upload server authentication via API Key
• New download API to download files from Upload server. Filetransfer is still supported but no longer required.
• RBAC rights per Organization
• Java project progress is now historized per organization
• Microsoft 365 assigned / used licenses are now historized
• Microsoft 365 app usage
• Support for Alpine Linux 3 for container scans.
  Due to missing functionality of the BusyBox environment in Alpine 3, only server scans under root are supported.
• Cloud licensing plan history.
  See the usage pattern of your cloud licenses over time.
• Performance improvements throughout the application
• Logging improvements
• Improvements for query development:
  Most queries in OctoWeb can now also be called by the Octopus2 GUI in query development mode.
  RBAC within queries can be simulated in Octopus2
• Query fieldsets provide macros for improved consistency of queries
• Improved Import Service for installations that require very low latency between scan and availability in the OctoSAM database.

Fixes

• Computer import from Active Directory did not filter out group-managed service accounts.

Changes

• Updated 3rd-Party Components
• Updated technical documentation
• Sample configuration files reorganized. All are now in Server/SampleConfigurationFiles and subdirectories thereof.

Scan file compatibility

• The 1.10.9 import service supports reading 1.10.9, 1.10.8, 1.10.7, and 1.10.6 scan files. Importing older .scan files is only partially supported for Windows systems with unsupported operating systems that cannot update to the newest scanner. Imported information may be incomplete for these systems.
• Linux systems under Microsoft Hyper-V need to update to the newest release scanner. Import of older scan files is not supported for this configuration.

Update instructions

Update from 1.10.8 to 1.10.9
When updating from an earlier version, see release notes of all versions in between

• For OctoSAM server installations, make sure you have the newest .net 8.0 hosting bundle installed.
• For the Octopus2 GUI client, ensure you have installed the newest .net 8.0 desktop runtime.
• Make sure your Browsers (Microsoft Edge or Google Chrome) are up to date.
• Stop OctoSAM services on the server
• Stop OctoWeb in IIS
• Make a backup copy of the database
• You can optionally run the .MSI Installer for the GUI client, but the preferred method is starting the GUI client from the Server/Octopus2 folder without installing the .MSI.
• Rename the existing Server folder.
• Copy the new Server folder from the installation media
• Migrate the database schema with the supplied migration script(s)
• Check your current appsettngs.json settings with the new sample file
  • consider switching to SSL-encrypted LDAP connections
• If you scan license management servers like FlexLM, please ensure the local tools are current. Use the newest tools provided by your servers.
• Update the repository (formerly Reports and Queries) from the provided .zip file in the Support subdirectory.
• Start OctoSAM services
• Make sure that full housekeeping was executed before trying to start the OctoSAM web interface.
  • Or use octoutil dbinit command
    
• Assign per organization privileges to your RBAC roles. Assign Organization.ALL.Read / Organization.ALL.Update to your existing roles.
• Analyze the Service log files for errors and warnings during initial imports and housekeeping.
• Update Octoscan2 Windows scanner
• After a successful update, remove the now obsolete renamed Server folder

Known limitations

• DPI scaling is in beta and does sometimes not work over RDP sessions, depending on the version of the server, the RDP client, and DPI settings on involved systems.
• FlexLM Diag scan supports only the first configured vendor daemon; the expiry date and other data scanned from diag are unavailable for other vendor daemons on the same FlexLM server.
• Reports with more than 2000 different software packages selected fail due to a limit in SQL Server.