What's New

Updates for 24.06

Following are the new features available in Lighthouse 24.06.

UI Enhancements

  • Updated user interface and work flows.

  • Reworked navigation and menus.

  • Updated styling and icons.

Connected Resource Gateway

  • New feature to build and manage a catalog of resources that are within the Smart Management Fabric (SMF) discovered networks.

  • Support for clientless network access to resources via either SSH, HTTP, or HTTPS proxy services.

  • Accessed via the new Resources page.

Resource Tagging

  • Support for user defined resource filters.

  • Support for user defined tags.

  • User group access control with resource filters.

  • Searching with Resource Filters.

  • Port Tags have been renamed to Resource Tags in the UI and API expanding it’s functionality to cover both Serial Ports and Resources.

Certificate Handling Enhancements

  • Automatic renewal of node and other certificates used to authenticate to Lighthouse.

  • Configuration of certificate management via the new cert_manage CLI command

AWS Lighthouse

  • For fresh AWS installs, a new default super user account lhadmin is provided and should be used for initial configuration.

  • By default, root login is now disabled over SSH for new installs. Existing AWS installs are unaffected.

  • By default, password authentication is now disabled over SSH. Existing AWS installs are unaffected.

  • Added support for AWS Lighthouse to allow login on IPv6-only subnets, enabling access for instances without public IPv4 addresses or any IPv4 addresses.

Smart Group Renaming

  • Smart Groups are now renamed to Node Filters within the Lighthouse UI. However, Smart Groups retain their naming within the CLI and API.

Updates for 24.06.2

Following are the new features available in Lighthouse 24.06.2

AWS Marketplace

Lighthouse is available on Amazon Web Services (AWS) Marketplace. You can subscribe to get access to our published AMIs, however, you must still contact Sales to obtain a license.

Third-Party Nodes

The Connect Resource Gateway can now be leveraged to proxy via SSH, HTTP or HTTPS to configure devices/third-party nodes.