You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Lumeta is pleased to introduce Lumeta Spectre Portal 3.2.6, which enables proxy support of Command Centers. This means that Lumeta Spectre Portal 3.2.6 now gives credentialed users either "view" access or "full" access to Command Centers behind a firewall. Portal users with valid credentials also gain the capability to run, operate, and manage multiple Command Centers from their Portal perspective. 

With proxy support, a single firewall opening permits Portal to communicate with connected Command Centers, negating the need for additional per-browser connections. Organizations that could not (or preferred not) to access their Command Centers directly due to firewall or policy restrictions now have an alternative means of access.

The alternative takes the form of a pass-through from Portal to Spectre with left- and right-click login options, as follows:

  • Left-click on a Command Center icon to open the selected Command Center with view (aka "read-only") access.
  • Right-click on a Command Center icon to log in to the selected Command Center with full access (aka "credential-based access" or "CBA") your user type (e.g., user, manager, admin).

Regardless of which method you use to open a Command Center, the Portal becomes a proxy for your web browser. Network traffic no longer flows from your web browser to the Command Center. Instead, it flows from your web browser, through the portal, and onto the Command Center.

The URL in the address bar indicates most (but not all) connections made via proxy by including /proxy/ in the address. In the example URL https://10.9.0.68/proxy/10.9.0.126/logbase/#/dashboards/e8cf0410-f968-4857-8dee-c21a9fd86110, the Portal 10.9.0.68 is behaving as the proxy to destination Command Center 10.9.0.126.  This means that the web browser is not communicating directly with the Command Center and that the Portal is acting as a proxy to the Command Center.

Portal maps are designed to show only Command Centers to which they have been connected, and the connection must be initiated at the Portal. This allows your organization to run standalone Command Centers with independent results that do not accrue at the Portal.

At log-out, all sessions are logged off and the Portal-connected user is returned to the Portal login screen from the location at which the logout was initiated (i.e., from Portal itself, from a read-only Command Center, or from a client-based authentication (CBA) Command Center.


  • No labels