Loading

Announcement

Skip Feed
  1. Upcoming enhancements to the UI:  

    1. Simplified Navigation 
    2. Ask Flexera 
    3. Manage Inactivity Timeout

     

    We are excited to share a set of upcoming UI enhancements designed to make your Flexera One experience simpler and more efficient. In June, you will see the following updates: 

     

     

    1. Simplified Navigation Experience 

    We are introducing the first phase of a redesigned navigation framework to improve usability. 

     

    What’s new: Frequently used, consistent items—such as Home, Dashboards, Reports, Administration, etc - will now appear at the top of the main navigation menu, in a dedicated section with a refreshed visual style. 

     

    What stays the same: Other navigation items will continue to appear below this section as they do today. 

     

    Why it matters: This update ensures faster, more consistent access to core areas of the platform. 

     

     

    2. Introducing “Ask Flexera” navigation item

    A new centralized hub for intelligent assistants is coming to your navigation. 

     

    What’s new: The Ask Flexera navigation item will bring together:  

    • ITAM Assistant 
    • Data Explorer 
    • GraphQL Query Generator 

    Why it matters: You’ll have a single, convenient place to access powerful tools that help you explore data, generate insights, and streamline workflows. 

     

     3. Configurable Inactivity Timeout 

    Organizations will soon have greater control over session management. 

     

    What’s new: Org Admins can configure inactivity timeout settings anywhere between 30 minutes and 6 hours. 

    Why it matters: This provides flexibility to align with your organization’s security and usability preferences, replacing the current fixed 30-minute timeout. 

     

     

    We will continue to roll out improvements and keep you informed every step of the way. Stay tuned for more updates as we enhance your experience! 

     

    For queries, please contact your Flexera representative.

    Expand Post

  2. Need to Know: Web Metering 2.0

     

    Release Date

    Web Metering 2.0 will be released as part of the FlexNet Inventory Agent 25.5.0 (2025 R2.5) on May 13 for Europe and APAC, and May 20 for the Americas.

    For the Snow Inventory Agent, it will be available in version 26.1.1 on June 10.

     

    What is it

    Web Metering 2.0 is an enhanced capability within Flexera that enables tracking of web application usage through browser extensions integrated with both the FlexNet and Snow agents.

    At its core, it introduces a new shared web metering module that operates across both agents, enabling direct communication between the browser extensions and the agent. This modern architecture replaces the previous file-based approach, resulting in a more secure and efficient data collection process.

     

    How it works

    Web Metering 2.0 improves the data flow by redefining how browser activity is captured and processed:

    • Browser extensions capture URLs visited by users
    • Data is sent directly to a local agent API over HTTP or HTTPS
    • The module filters and processes URLs using Allow List rules
    • Only relevant and sanitized data is retained and passed to the agent
    • The agent consolidates the processed data and sends it upstream for SaaS usage recognition

     

    What has changed

     

    No raw browsing data stored on disk

    URLs are now processed before being stored. Previously, raw browsing activity was cached on disk before being processed by the agent.

     

    Stronger protection of sensitive data

    Query parameters are removed from URLs by default. Enhanced Allow List rules control what data is retained and apply masking when Personal Information is detected.

     

    Direct communication between extension and agent

    The new web metering module introduces a write-only, machine-local API endpoint running on 127.0.0.1:40400, which is not externally accessible. TLS can be configured to encrypt communication between the browser extension and the agent.

     

    Improved troubleshooting

    The new module allows testing of URL matching and sensitive data removal directly from the command line.

     

    Improved browser coverage

    This design restores support for Apple Safari following previous limitations on extension-generated data.

    The Firefox extension is now available in the Mozilla store, improving the installation and update experiences.

     

    Consistent implementation across agents

    A single, shared web metering module is used across both FlexNet and Snow agents, helping standardize behaviour and simplify deployment.

     

    Security considerations

     

    Web Metering 2.0 is designed with a strong security-first approach to ensure customer environments remain protected while delivering accurate SaaS usage insights.

    The solution uses a machine-local, non-externally accessible communication mechanism, ensuring no additional external services or attack surfaces are introduced. TLS can be enabled to further secure communication between browser extensions and the agent.

    Sensitive data exposure is minimized through filtering, masking, and by avoiding unnecessary data storage.

    Importantly, the feature is fully customer-controlled and opt-in, preserving existing trust boundaries and ensuring organizations maintain complete control over their data and deployment.

    Expand Post

  3. Need to Know: Web Metering 2.0

     

    Release Date

    Web Metering 2.0 will be released as part of the FlexNet Inventory Agent 25.5.0 (2025 R2.5) on May 13 for Europe and APAC, and May 20 for the Americas.

    For the Snow Inventory Agent, it will be available in version 26.1.1 on June 10.

     

    What is it

    Web Metering 2.0 is an enhanced capability within Flexera that enables tracking of web application usage through browser extensions integrated with both the FlexNet and Snow agents.

    At its core, it introduces a new shared web metering module that operates across both agents, enabling direct communication between the browser extensions and the agent. This modern architecture replaces the previous file-based approach, resulting in a more secure and efficient data collection process.

     

    How it works

    Web Metering 2.0 improves the data flow by redefining how browser activity is captured and processed:

    • Browser extensions capture URLs visited by users
    • Data is sent directly to a local agent API over HTTP or HTTPS
    • The module filters and processes URLs using Allow List rules
    • Only relevant and sanitized data is retained and passed to the agent
    • The agent consolidates the processed data and sends it upstream for SaaS usage recognition

     

    What has changed

     

    No raw browsing data stored on disk

    URLs are now processed before being stored. Previously, raw browsing activity was cached on disk before being processed by the agent.

     

    Stronger protection of sensitive data

    Query parameters are removed from URLs by default. Enhanced Allow List rules control what data is retained and apply masking when Personal Information is detected.

     

    Direct communication between extension and agent

    The new web metering module introduces a write-only, machine-local API endpoint running on 127.0.0.1:40400, which is not externally accessible. TLS can be configured to encrypt communication between the browser extension and the agent.

     

    Improved troubleshooting

    The new module allows testing of URL matching and sensitive data removal directly from the command line.

     

    Improved browser coverage

    This design restores support for Apple Safari following previous limitations on extension-generated data.

    The Firefox extension is now available in the Mozilla store, improving the installation and update experiences.

     

    Consistent implementation across agents

    A single, shared web metering module is used across both FlexNet and Snow agents, helping standardize behaviour and simplify deployment.

     

    Security considerations

     

    Web Metering 2.0 is designed with a strong security-first approach to ensure customer environments remain protected while delivering accurate SaaS usage insights.

    The solution uses a machine-local, non-externally accessible communication mechanism, ensuring no additional external services or attack surfaces are introduced. TLS can be enabled to further secure communication between browser extensions and the agent.

    Sensitive data exposure is minimized through filtering, masking, and by avoiding unnecessary data storage.

    Importantly, the feature is fully customer-controlled and opt-in, preserving existing trust boundaries and ensuring organizations maintain complete control over their data and deployment.

    Expand Post

  4. Official release of FlexNet Inventory Agent 25.5.0

     

    We are pleased to announce the release of the FlexNet Inventory Agent 25.5.0.

    Release Date: EU/AP: 2026-05-13, NA: 2026-05-20

     

    This release includes:

      

    • Support for Unicode file names in PVU hardware inventory
    • Verified inventory collection support for AWS Bottlerocket Linux
    • New file size and publisher fields in agent usage (.mmi) file
    • Least privilege mode support for the Kubernetes agent
    • High-availability support for multiple KRM controllers
    • Configurable limit for concurrent KRM image scans
    • Improved collection of browser extension URL data for web metering
    • Improved web metering URL processing for sensitive query parameters
    • Fix for containerd inventory scan being skipped when Podman scanning is enabled
    • Fix for backslash characters being replaced in beacon authentication usernames on UNIX-like operating systems
    • Fix for Java version information being ignored
    • Fix for missing diagnostic detail when an agent upgrade package fails signature verification
    • Fix for ndtrack crash caused by invalid macOS bundle plist data
    • Bundled software version updated

     

    Customer Impact:

     

    • Previously, some PVU hardware inventory files with Unicode characters in the filename (for example, usernames containing accented characters) could be skipped during processing. Now, these inventory files are handled correctly. This enhancement helps prevent unnecessary creation of duplicate inventory files.
    • Inventory collection support for Bottlerocket Linux environments has been verified for the Flexera Kubernetes Inventory Agent (KRM) and the Linux inventory agent. This enhancement provides clearer deployment guidance for Kubernetes environments using Bottlerocket.
    • Previously, the agent usage file (.mmi) did not include file size and publisher information. Now, the .mmi output includes these additional fields. This enhancement improves the usefulness of usage data for some reporting scenarios.
    • Previously, the Kubernetes agent required elevated privileges to run, which could be a blocker in environments with strict security policies. Now, the Kubernetes agent can be run in a least privilege mode. This enhancement supports improved security posture and broader deployability.
    • Previously, Kubernetes agent deployments did not support configuring multiple controllers in a high availability pattern. Now, multiple KRM controllers can be deployed so that only one is active while others remain passive and can take over if needed. This enhancement supports high availability requirements and improves resilience.
    • Previously, the Kubernetes agent could initiate an unlimited number of concurrent container inventory scans when first deployed, which could result in a high volume of simultaneous requests to the Kubernetes API server. Now, the number of concurrent container inventory scans is limited to 10 by default. This limit is configurable to suit the environment's requirements.
    • Previously, collecting web metering URL data from browser extensions had limitations in some environments (including Safari) and required approaches that were harder to standardize across browsers. Now, the solution for obtaining URL data has been improved and unified across supported browsers. This enhancement improves compatibility and supports future security and processing improvements.
    • NOTE: This enhancement requires the updated browser extensions. The previous browser extensions are not compatible with this release.
    • Previously, web metering URL collection could include unnecessary query parameter values that might contain sensitive information. Now, URL processing supports masking or dropping sensitive query parameters according to updated allowlist rules. This enhancement helps reduce privacy risk and unnecessary data transmission.
    • Previously, enabling both containerd inventory scanning and Podman inventory scanning on the FlexNet Inventory Agent for Linux could cause containerd inventory collection to be skipped. This release resolves this issue.
    • Previously, usernames containing backslash (\) characters (for example, in domain\user formats) could be rewritten with forward slashes (/) when applying configuration on UNIX-like operating systems. This release resolves this issue.
    • Previously, valid Java version information could be ignored if the java -version command returned a non-zero exit code, even when the version output was present. This release resolves this issue.
    • Previously, if a downloaded upgrade package failed signature verification, the agent logs could provide only a generic "Signature check failed" message without additional detail. This release resolves this issue.
    • Previously, the FlexNet Inventory Agent for macOS could crash when reading certain bundle .plist files containing embedded newlines or carriage returns in key fields. This release resolves this issue.
    • The OpenSSL, Go, Moby (replaced Docker), Podman, and Kubernetes third party libraries bundled with the agent have been updated in this release to address security vulnerabilities.

     

    IMPORTANT

     

    This release updates the Docker client library to be compatible with Docker Engine 29.3.x and 29.4.x. The update requires Docker Engine API version 1.40 or later to be present on the machine running fnms-docker-monitor. Docker versions 18 and 19, which use Docker Engine API version 1.39, are no longer supported. If the installed Docker Engine does not meet this requirement, fnms-docker-monitor will be unable to connect to the Docker API and will not collect any inventory data.

     

    Product Documentation: Agent Documentation 

    Please find more about the content of this release in the Release Notes.

    Expand Post

  5. MSP Users Access Management with Access Policies in Flexera One – Early Access

    Release date: April 28, 2026

     

    We’re excited to announce the Early Access release of MSP Users Access Management with Access Policies in Flexera One, enabling MSP partners to centrally manage and enforce user access across customer environments using consistent, policy-based controls. This enhancement strengthens governance while simplifying how MSPs administer user permissions at scale. 

     

    Value Outcomes

    • Reduced administrative effort through centralized, policy-based access management
    • Improved security and compliance via consistent access enforcement
    • Better scalability for MSP operations as customer and user volumes grow
    • Increased confidence for both MSPs and customers in how access is governed within Flexera One 

     

    Please reach out to your Flexera representative if you would like to join Early Access. Documentation can be provided upon request.

    Expand Post

  6. North America Organizations: Inventory Beacon Release 25.4.0 - Conversion of FlexNet Beacon to a 64-bit application - Action needed!

    The April 2026 update for North American organizations changes FlexNet Beacon from a 32-bit to a 64-bit application. Version 25.3.0 that included the 32-bit to 64-bit change was released to organizations in other regions but skipped in North America. For organizations with automatic upgrade of the Beacon turned on, Flexera One will bump the version to the latest available automatically – 25.4.0. Version 25.3.0 will however still be available for download from the Beacon Versions page in Flexera One.

    If your organization has automatic Beacon upgrades active, or if you want to manual upgrade your Beacons to the latest version, please first refer to our previous post about the version upgrade and the required steps to ensure that you don't have any breaking changes.

    Expand Post

  7. Introducing Web Metering 2.0

    Re‑architected for Security, Enhanced Privacy, and Safari Support Is Back

     

    We’re pleased to announce Web Metering 2.0, a significant enhancement to web application metering for FlexNet and Snow agents. This release introduces a newly re‑architected browser data ingestion pipeline, delivering stronger security, improved privacy protections, and expanded browser support—including the return of Apple Safari.

     

    What’s New in Web Metering 2.0

    Web Metering 2.0 has been redesigned from the ground up to provide a more secure and privacy‑focused experience while maintaining reliable usage insights.

    Key benefits include:

    • 🔐 Enhanced Security
    • Improved protections across browser data collection and ingestion.
    • 🛡️ Reduced PII Collection
    • Optimized data handling to minimise the capture of Personally Identifiable Information (PII).
    • 🌍 Expanded Browser Support
    • Full support for Apple Safari, alongside Google Chrome, Microsoft Edge, and Mozilla Firefox.

     

    What You Need to Know

    To use Web Metering 2.0, customers must deploy both a new agent version and the new Web Metering browser extensions.

    Required Agent Versions

    • FlexNet Agent: Available in v25.5.0 (scheduled for May release)
    • Snow Agent: Available in v26.1.1 (scheduled for June release)

    Important:

    Existing agent versions are only compatible with the current browser extensions.

    The new extensions labelled “Flexera Web Metering” will work only with the agent versions listed above and later.

     

    🌐 Current Browser Extension Downloads

    Please continue using the following extensions until the new version of the agents are released.

    Expand Post

    mag00_75 likes this.
    1 of 9
    • @Gabriel Carvalho (Flexera Software)​ , thanks for this. It looks like this is in a different category of comms to this thread, so it was difficult to track down. For people following this thread, this is available here > https://community.flexera.com/s/feed/0D5PL00000rqzsK0AQ

       

      I do have some follow up questions that I would be asking from an Infosec lens, that are not addressed in the further communications or documentation as I have seen, as below >

       

      • How does the agent know the request is coming from the Flexera browser extension and not another program? s there a secret token or key exchanged between the browser extension and the agent? How is that token generated, stored, and rotated?
      • Does the agent check who is sending the request?Does the agent validate the Origin header and reject requests that don't come from the official browser extension?
      • Is the endpoint guaranteed to only listen on the local machine?How is the agent configured to ensure it only listens on 127.0.0.1? Is this enforced in code or just a configuration setting that could be changed?
      • What happens if something else is already using port 40400 when the agent starts? How does the agent handle port conflicts on startup?
      • Does the endpoint send any data back to the browser extension? What does the HTTP response contain? Is it limited to a simple success or failure status code, with no additional data?
      • Are requests to the API logged? 
      • Is there a limit on how many requests can be sent to the endpoint? Without a limit, a bug in the browser extension….or a malicious program..could flood the agent with thousands of requests per second, potentially causing it to crash or consume excessive system resources
      Expand Post

  8. Introducing Web Metering 2.0

    Re‑architected for Security, Enhanced Privacy, and Safari Support Is Back

     

    We’re pleased to announce Web Metering 2.0, a significant enhancement to web application metering for FlexNet and Snow agents. This release introduces a newly re‑architected browser data ingestion pipeline, delivering stronger security, improved privacy protections, and expanded browser support—including the return of Apple Safari.

     

    What’s New in Web Metering 2.0

    Web Metering 2.0 has been redesigned from the ground up to provide a more secure and privacy‑focused experience while maintaining reliable usage insights.

    Key benefits include:

    • 🔐 Enhanced Security
    • Improved protections across browser data collection and ingestion.
    • 🛡️ Reduced PII Collection
    • Optimized data handling to minimise the capture of Personally Identifiable Information (PII).
    • 🌍 Expanded Browser Support
    • Full support for Apple Safari, alongside Google Chrome, Microsoft Edge, and Mozilla Firefox.

     

    What You Need to Know

    To use Web Metering 2.0, customers must deploy both a new agent version and the new Web Metering browser extensions.

    Required Agent Versions

    • FlexNet Agent: Available in v25.5.0 (scheduled for May release)
    • Snow Agent: Available in v26.1.1 (scheduled for June release)

    Important:

    Existing agent versions are only compatible with the current browser extensions.

    The new extensions labelled “Flexera Web Metering” will work only with the agent versions listed above and later.

     

    🌐 Current Browser Extension Downloads

    Please continue using the following extensions until the new version of the agents are released.

     

    Expand Post

End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
2 Followers
49 Posts
9 members are discussing this topic.
Loading
Announcement | Flexera